You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jeff Schnitzer (JIRA)" <ji...@codehaus.org> on 2015/02/04 20:26:18 UTC
[jira] (MNG-5761) picks wrong version for
transitive dependencies
Jeff Schnitzer created MNG-5761:
-----------------------------------
Summary: <dependencyManagement> picks wrong version for transitive dependencies
Key: MNG-5761
URL: https://jira.codehaus.org/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 guice 18
guice-parent's dependencyManagement specifies guice 16
Guice 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.1.6#6162)