maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schulte (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (MRESOLVER-9) DefaultDependencyCollector does not correctly handle dependency management.
Date Sun, 11 Dec 2016 00:20:58 GMT

     [ https://issues.apache.org/jira/browse/MRESOLVER-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christian Schulte closed MRESOLVER-9.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: Maven Artifact Resolver 1.2.0

Fixed with [this|https://git-wip-us.apache.org/repos/asf?p=maven-resolver.git;a=commit;h=1ee92862c67ec98564c4d8be1207355960f1dd5d]
commit.

> 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
>            Assignee: Christian Schulte
>            Priority: Critical
>             Fix For: Maven Artifact Resolver 1.2.0
>
>
> 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.4#6332)

Mime
View raw message