[ 
https://issues.apache.org/jira/browse/MNG-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889942#comment-17889942
 ] 

Christian Schulte commented on MNG-5761:
----------------------------------------

[~Didier Loiseau] Indifference, not bitterness.

parent
- module1
- module2

Build in parent, get a different dependency tree. Build in module1, get a 
different dependency tree. Build in module2, get a different dependency tree. 
What build system is that, not fixing a key feature for more than a decade and 
not even now. Requested by various users independently for Maven 2, Maven 3, 
Maven 4 and what not. Repeatedly reported. Repeatedly closed won't fix. 
Repeatedly reopened. Ridiculous. Has driven away lots of users. Those said 
"millions of users" never existed. Received a lot of justified rants for things 
like this.

> 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
>            Priority: Critical
>             Fix For: 4.0.x-candidate
>
>         Attachments: MNG-5761.zip, depending-pom2.xml
>
>
> 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
(v8.20.10#820010)

Reply via email to