You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/06/13 04:51:12 UTC
[jira] Updated: (MNG-3038) Transitive DepMan not working (per
MNG-1577) [use case attached]
[ http://jira.codehaus.org/browse/MNG-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3038:
------------------------------
Fix Version/s: (was: 2.1-alpha-1)
2.1
> 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: Artifacts and Repositories
> Affects Versions: 2.0.5, 2.0.6
> Reporter: Joakim Erdfelt
> Assignee: Patrick Schneider
> Fix For: 2.1
>
> 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