You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2014/06/12 05:39:10 UTC

[jira] (MNG-3038) Transitive DepMan not working (per MNG-1577) [use case attached]

     [ https://jira.codehaus.org/browse/MNG-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl closed MNG-3038.
------------------------------

    Resolution: Cannot Reproduce

> Transitive DepMan not working (per MNG-1577) [use case attached]
> ----------------------------------------------------------------
>
>                 Key: MNG-3038
>                 URL: https://jira.codehaus.org/browse/MNG-3038
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.5, 2.0.6
>            Reporter: Joakim Erdfelt
>            Assignee: Patrick Schneider
>             Fix For: Issues to be reviewed for 3.x
>
>         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 was sent by Atlassian JIRA
(v6.1.6#6162)