[
https://issues.apache.org/jira/browse/MNG-5947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15080541#comment-15080541
]
ASF GitHub Bot commented on MNG-5947:
-------------------------------------
Github user akacme commented on the pull request:
https://github.com/apache/maven/pull/74#issuecomment-168543843
Perhaps a POM property with predefined name could activate this behaviour
in 3.x? In this way it can be set on a per-project basis as well as global
(with properties injected via settings.xml).
In case when a change of DependencyManagement model is allowed (4.x?) -
this might be better approach in the long run as this info can be reused in the
maven dependency plugin (to show where managed version comes from) and perhaps
will allow to introduce pluggable dependency resolution strategy
(nearest-match, newest-version, etc.) in both dependency and
dependencyManagement sections.
> 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)
