[IVY-613] Missing configurations with different version-wildcards dependencies to same dependent version

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.4.1
• Fix Version/s: 2.0.0-alpha-1
• Component/s: Core
• Assignee: Maarten Coene
• Reporter: Johannes Stamminger
• Created: 28/Sep/07 11:28
• Updated: 16/Apr/08 21:47
• Resolved: 16/Apr/08 21:47

Description

1) with resolving to exactly one version:

moduleA depends libX-1.+ in conf U
moduleA depends moduleB in conf U,V
moduleB depends libX-[1.5,) in conf U,V
(conf mappings straight forward, U,V->@)

Lates libX version in the repo is e.g. 1.7

We would expect to get 1.7 included in configurations U and V.
But it is included only in U.

2) with resolving to two versions with similar configurations:

moduleA depends libX-1.+ in conf U
moduleA depends moduleB in conf U,V
moduleB depends libX-1.5 in conf U,V <<< different to 1!
(conf mappings straight forward, U,V->@)

Lates libX version in the repo is e.g. 1.7, 1.5 availble. too. Both contain a configuration U and V.

We would expect to get 1.7 included in configurations U and V.
But it is included only in U.

3) with resolving to two versions with different configurations:

moduleA depends libX-1.+ in conf U
moduleA depends moduleB in conf U,V
moduleB depends libX-1.5 in conf U,V <<< different to 1!
(conf mappings straight forward, U,V->@)

Lates libX version in the repo is e.g. 1.7, 1.5 availble. too. Now with 1.7 containing only conf U, 1.5 having U and V

Here I'm not sure of the "correct" behaviour ... ?