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

Maven 2

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

Created: 06/Jun/07 11:23 AM Updated: 12/Jun/08 09:49 PM

Component/s:

Artifacts and Repositories

Affects Version/s:

2.0.5, 2.0.6

Fix Version/s:

3.0

Time Tracking:

Not Specified

File Attachments:

carlos_transitive_version.tar.gz (0.6 kb)

Issue Links:

Related

This issue relates to:

~~MNG-1577~~ dependencyManagement does not work for transitive dependencies

Description

« Hide

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)

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Joakim Erdfelt - 07/Jun/07 03:36 PM

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

[ Permlink | « Hide ]

Joakim Erdfelt - 07/Jun/07 09:12 PM

The integration test IT0121 demonstrates this use case.

[ Permlink | « Hide ]

Joakim Erdfelt - 07/Jun/07 09:15 PM

Another use case.

You have 4 projects. A,B,C,D

You have the following defined. (where notation is in the form [Project] -> [Dependency])

A -> B
A -> C
B -> D
C -> D

This forms a graph shaped like a diamond.

The following dependency management sections are defined in the above graph.
B has a depMan that says D version 2.0
C has a depMan that says D version 1.0

What version of D is in use at project A ?