Details
-
Type:
Bug
-
Status:
In Progress
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.0.5, 2.0.6
-
Fix Version/s: Issues to be reviewed for 3.x
-
Component/s: Artifacts and Repositories
-
Labels:None
-
Number of attachments :
Description
When working with the example use case described by Carlos on the MNG-1577 thread.
http://www.nabble.com/Re%3A--vote--MNG-1577-as-the-default-behavior-p9506667s177.html
What about this use case for transitive dependencyManagement? has been tested? A -> B -> C -> D C depends on D 1.0 B has D 2.0 in dependencyManagement, no D in dependencies A should get D 2.0
It was discovered that this does not work.
Sample Project / Use Case is attached. (655 bytes)
This will likely not be fixed for maven 2.0.x
Instead it will be taken as an example use case for the 2.1 artifact resolution specification.
http://docs.codehaus.org/display/MAVEN/Maven+2.1+Artifact+Resolution+Specification