[ https://issues.apache.org/jira/browse/MNG-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15781478#comment-15781478 ]
Hudson commented on MNG-5761: ----------------------------- SUCCESS: Integrated in Jenkins build maven-plugins #8052 (See [https://builds.apache.org/job/maven-plugins/8052/]) [MNG-5761] Dependency management is not transitive. o Updated to disable this IT for Maven >= 3.4. As long as the model version 5.0.0 PDT file is not implemented, it makes no sense to assert resolution results to remain permanent accross decades of Maven versions. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1776212]) * (edit) maven-dependency-plugin/src/it/projects/tree/invoker.properties > Dependency management is not transitive. > ---------------------------------------- > > 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 > Assignee: Christian Schulte > Priority: Critical > Fix For: 3.4.0 > > Attachments: MNG-5761.zip > > > 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)