[
https://issues.apache.org/jira/browse/MNG-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545673#comment-14545673
]
Jon Stevens commented on MNG-5761:
----------------------------------
I agree with Maria and she shouldn't have to apologize for expressing her
totally valid opinion!
Jason, you're acting like I used to act when I was a dick back in the day when
we used to work together. The difference is that I got wise and learned that
that behavior just doesn't fly in the real world and honestly really isn't
necessary.
Please apologize, re-open the issue and work with Jeff to solve things. It is
in the best interest of everyone.
Smooches.
-jon
> <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
> Assignee: Jason van Zyl
>
> 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)