[
https://issues.apache.org/jira/browse/MNG-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543235#comment-14543235
]
Maria Petridean commented on MNG-5761:
--------------------------------------
The description of this issue here, does not match 100% the description on
stackoverflow. I encountered the same issue: a project A with a parent pom
which has a dependencyManagement section (everything ok until now). Then,
another project B, depends on project A and the result is that the
dependencyManagement section in A'a parent pom is ignored for resolving the
transitive dependencies.
Could you update the description of this issue to reflect also this case?
> <dependencyManagement> picks wrong version for transitive dependencies
> ----------------------------------------------------------------------
>
> Key: MNG-5761
> URL: https://issues.apache.org/jira/browse/MNG-5761
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.2.5
> Reporter: Jeff Schnitzer
>
> A detailed description of the issue is here:
> http://stackoverflow.com/questions/28312975/maven-dependencymanagement-version-ignored-in-transitive-dependencies
> The short of it is that maven appears to be using the wrong
> <dependencyManagement> version in a transitive dependency. There are two
> relevant <dependencyManagement> sections in the build, one pulled in by guice
> and one pulled in by gwizard-parent. These are the dependency paths from the
> top:
> gwizard-example -> gwizard-config -> gwizard-parent
> gwizard-example -> gwizard-config -> guice -> guice-parent
> gwizard-parent's dependencyManagement specifies guava 18
> guice-parent's dependencyManagement specifies guava 16
> Guava 16 is winning. This seems highly undesirable, and in fact it breaks our
> build. I would expect that in a version # fight, "closest to the top" should
> win.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
