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

Jason van Zyl commented on MNG-5761:
------------------------------------

No. There are over 200 hundred issues and I prioritize looking at issues with 
working examples, tests, and integration tests. If someone can't spend the time 
required to at least put together a working example of the problem, it's highly 
unlikely I'm going to look at it and will fall into the range of not being 
looked at for a year at which point I close them. If I were not the only one 
generally looking at these issues I would leave it open. But there are only 5 
people who might be able to fix this and I know the 4 others won't be looking 
at it anytime soon.

So I just save myself the hassle and I find it's a good filter. If you're not 
going to put in X to make something workable, why would I put in the 3-10X to 
look at even attempt to fix. If you want it looked at spend the time making a 
working example. I spend a lot of time processing issues with PRs and tests as 
I try to respect the time of those people who put in the effort to get their 
issues looked at. 

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

Reply via email to