maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-5761) Dependency management is not transitive.
Date Fri, 30 Dec 2016 15:46:58 GMT

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

Hudson commented on MNG-5761:
-----------------------------

SUCCESS: Integrated in Jenkins build maven-plugins #8235 (See [https://builds.apache.org/job/maven-plugins/8235/])
[MNG-5761] Dependency management is not transitive.

o Updated to add a missing test dependency (used but undeclared) managed to
  non-transitive test scope transitively. The compilation error without
  that declaration in fact is expected behaviour. Don't let them fool you.

  I can build all plugins using 3.4.0-SNAPSHOT by upgrading the plugin tools
  manually on the command line like:

  mvn -DmavenPluginToolsVersion=3.5 test-compile (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1776591])
* (edit) maven-clean-plugin/pom.xml


> 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
>             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)

Mime
View raw message