You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/12/13 23:08:58 UTC
[jira] [Commented] (MNG-5761) Dependency management is not
transitive.
[ https://issues.apache.org/jira/browse/MNG-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746559#comment-15746559 ]
Hudson commented on MNG-5761:
-----------------------------
SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #38 (See [https://builds.apache.org/job/maven-3.x%20Jigsaw/38/])
[MNG-5761] Dependency management is not transitive. (schulte: rev cc5af1306ff91d9bef68737c96c364a371a477d7)
* (edit) maven-compat/src/test/java/org/apache/maven/artifact/AbstractArtifactComponentTestCase.java
* (edit) maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/MavenRepositorySystemUtils.java
> 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
> Assignee: Christian Schulte
> Priority: Critical
> Labels: requires-aether-release
> Fix For: 3.4.0
>
> Attachments: MNG-5761.zip
>
>
> 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)