maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maria Petridean (JIRA)" <>
Subject [jira] [Commented] (MNG-5761) <dependencyManagement> picks wrong version for transitive dependencies
Date Thu, 03 Mar 2016 10:10:18 GMT


Maria Petridean commented on MNG-5761:

I just ran into the same problem again. The coincidence is that I also try to enforce commons-collections
This issue should really be re-opened as it is a bug which should be fixed.

> <dependencyManagement> picks wrong version for transitive dependencies
> ----------------------------------------------------------------------
>                 Key: MNG-5761
>                 URL:
>             Project: Maven
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 3.2.5
>            Reporter: Jeff Schnitzer
>            Assignee: Jason van Zyl
>         Attachments:
> A detailed description of the issue is here:
> 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

View raw message