[
https://issues.apache.org/jira/browse/MNG-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887170#comment-17887170
]
Christian Schulte commented on MNG-5761:
----------------------------------------
DefaultDependencyManager goes back to Maven 3.4, which never got released. So
this is what should have been the default behaviour from day one. I am no
longer doing Java development. To make a long story short. I took a look at the
Jira issues somewhen 2015 or so - one of those you seem to have reopened - and
just fixed inconsistencies, bugs and such. This was not possible due to
integration tests starting to fail - no matter if the test was testing correct
behaviour or not. It was then decided to reset almost all of my work and retain
behaviour - even if inconsistent or just not behaving as advertised. I kept a
3.4-SNAPSHOT version in my private Github repository. You can download it from
there and you will soon get, why nothing of that will ever land in an official
release. When it was clear, there will be no more changes in resolution
behaviour for pom 4.0, I added some warning messages as well. That's the
version I did run locally somewhen 7 years ago and I would run locally, when I
would still be doing Java things. I do not even know, if it still works at all.
I read the notification mail by accident, when configuration my spam filter.
[3.4-SNAPSHOT|https://github.com/ChristianSchulte/maven/releases/tag/2017-11-27]
> 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)
