Comment 1 Christian Schulte 2016-01-28 11:27:58 EST

During dependency processing the 'DependencySelector' is called to decide if a dependency is to be selected. The call to 'DependencySelector.selectDependency( dependency )' is performed with the unmanagement dependency but needs to be performed with the managed dependency. See the attached patch. With this patch applied, the result no longer contains dependencies whose scope or optionality has been managed to not be part of the result (correct behaviour). Without this patch applied, the result contains dependencies with a managed scope or optionality not filtered out by the 'DependencySelector' in use (incorrect behaviour).

Comment 2 Christian Schulte 2016-01-28 11:30:46 EST

Created attachment 259437 [details]
Patch correcting the order 'DependencyManager' and 'DependencySelector' are called.