maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Schnitzer (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-5761) <dependencyManagement> picks wrong version for transitive dependencies
Date Wed, 04 Feb 2015 23:24:18 GMT

     [ https://jira.codehaus.org/browse/MNG-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jeff Schnitzer updated MNG-5761:
--------------------------------

    Description: 
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.

  was:
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.


> <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 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.1.6#6162)

Mime
View raw message