[
http://jira.codehaus.org/browse/MNG-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98777
]
Joakim Erdfelt commented on MNG-3038:
-------------------------------------
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
> Transitive DepMan not working (per MNG-1577) [use case attached]
> ----------------------------------------------------------------
>
> Key: MNG-3038
> URL: http://jira.codehaus.org/browse/MNG-3038
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.5, 2.0.6
> Reporter: Joakim Erdfelt
> Attachments: carlos_transitive_version.tar.gz
>
>
> 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
> {noformat}
> 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
> {noformat}
> It was discovered that this does not work.
> Sample Project / Use Case is attached. (655 bytes)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
