[MNG-1207] Recursive dependencies with exclusive bounds fail

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.0 (RC)
• Fix Version/s: 2.0
• Component/s: Artifacts and Repositories
• Assignee: Unassigned
• Reporter: Garrett Conaty
• Created: 15/Oct/05 00:37
• Updated: 01/Feb/06 14:44
• Resolved: 20/Oct/05 09:59

Description

ResolutionNode.getDependencyTrail calls artifact.selectVersion(artifact.getSelectedVersion()) even w/o checking artifact.isSelectedVersionKnown().

It should perhaps have the same handling as DefaultArtifactCollector.recurse(...) which uses retrieveAvailableVersions or getAvailableVersions to then call artifact.getVersionRange().matchVersion(...)

Example:

A depends on B which depends on C

if B depends on C version (1.0,1.1)
then B resolves the dependencies fine.
However, if you try to build A, then maven tries to look for C-1.1.jar which is of course outside B's dependency version.