[jira] [Commented] (MRESOLVER-9) DefaultDependencyCollector does not correctly handle dependency management.

["Christian Schulte (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MRESOLVER-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942043#comment-15942043 ] 

Christian Schulte commented on MRESOLVER-9:
-------------------------------------------

Issue is fixed in the master branch of [my private maven repository on github|https://github.com/ChristianSchulte/maven-resolver/tree/master]. When interested, you can cherry pick the commit to your own repository and create a pull request for the apache master branch with just this commit yourself from there.

> DefaultDependencyCollector does not correctly handle dependency management.
> ---------------------------------------------------------------------------
>
>                 Key: MRESOLVER-9
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-9
>             Project: Maven Resolver
>          Issue Type: Bug
>            Reporter: Christian Schulte
>            Priority: Critical
>             Fix For: Maven Artifact Resolver 1.2.0 pre-reset
>
>
> 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. With the fix applied, the result no longer contains dependencies whose scope or optionality has been managed to not be part of the result (correct behaviour). Without the fix applied, the result contains dependencies with a managed scope or optionality not filtered out by the 'DependencySelector' in use (incorrect behaviour).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)