Michał Kowalcze created MNG-5947:
------------------------------------
Summary: 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
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 and
declared)
* parent:3.2.2:pom with commons-collections:3.2.2 (in dependencyManagement and
declared)
* import:1.0:pom with dependencyManagement importing parent:3.21
* final:1.0:pom with dependencyManagement importing import: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)
