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

Maria Petridean edited comment on MNG-5761 at 5/15/15 5:46 AM:
---------------------------------------------------------------

Thanks for the quick answer and involvement. But I agree that "Cannot 
Reproduce" is not a good resolution for this issue, given that it really can be 
reproduced. My suggestion, if I may have one, is to leave it "Open" and create 
a Jira label to mark this as 'on hold' until a sample project is attached or 
until someone will make the time (or is there a resolution in Jira for 'on 
hold'? This would seem fair. 'cannot reproduce' does not actually reflect the 
reality and nobody will look again over it if it sees this resolution) Sorry, i 
don't mean to upset anyone, i can understand the short time and the many 
reported bugs; still, i think there should be suitable resolutions, statuses 
and priorities for all cases.


was (Author: maria.petridean):
I agree that "Cannot Reproduce" is not a good resolution for this issue, given 
that it really can be reproduced. My suggestion, if I may have one, is to leave 
it "Open" and create a Jira label to mark this as 'on hold' until a sample 
project is attached or until someone will make the time (or is there a 
resolution in Jira for 'on hold'? This would seem fair. 'cannot reproduce' does 
not actually reflect the reality and nobody will look again over it if it sees 
this resolution) Sorry, i don't mean to upset anyone, i can understand the 
short time and the many reported bugs; still, i think there should be suitable 
resolutions, statuses and priorities for all cases.

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