maven-issues mailing list archives

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

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

Hudson commented on MRESOLVER-9:
--------------------------------

SUCCESS: Integrated in Jenkins build maven-wagon #1320 (See [https://builds.apache.org/job/maven-wagon/1320/])
[MRESOLVER-9] DefaultDependencyCollector does not correctly handle (schulte: rev f244ece2eee01500e4b1bc334b8dcd35b47f9422)
* (edit) pom.xml
* (edit) wagon-tcks/wagon-tck-http/pom.xml


> 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