[
https://issues.apache.org/jira/browse/MNG-5947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15080624#comment-15080624
]
ASF GitHub Bot commented on MNG-5947:
-------------------------------------
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/74#issuecomment-168565897
POM property, CLI property override, or we might want to start collecting
these provisional changes in a special maven plugin configuration section for
activating proposed features in Maven 4.x that 3.x users can try at their
convenience. There are quite a few things stacking up so I think a plugin
configuration can act as a feature toggle of sorts so that we don't affect
existing users but easily allow the adventurous to try things out.
> dependencyManagement import section does not resolve dependencies using
> "nearest" definition
> --------------------------------------------------------------------------------------------
>
> Key: MNG-5947
> URL: https://issues.apache.org/jira/browse/MNG-5947
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.3.3
> Reporter: Michał Kowalcze
> Attachments: MNG-5947-poms.tgz
>
>
> While resolving dependencies for dependencyManagement version of a particular
> dependency is determined using "first match", not "nearest" definition.
> Assuming that we have:
> * parent:3.2.1:pom with commons-collections:3.2.1 in dependencyManagement
> * parent:3.2.2:pom with commons-collections:3.2.2 in dependencyManagement
> * imported:1.0:pom with dependencyManagement importing parent:3.21
> * final:1.0:pom with dependencyManagement importing imported:1.0 and
> parent:3.2.2
> then dependency version for commons-collections in the final POM is set to
> 3.2.1 (as import 1.0 / parent 3.2.1 is first match), not 3.2.2 which is
> nearer (one level of import vs. two levels for 3.2.1).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
