Recursive dependencies with exclusive bounds fail
-------------------------------------------------
Key: MNG-1207
URL: http://jira.codehaus.org/browse/MNG-1207
Project: Maven 2
Type: Bug
Components: maven-artifact
Versions: 2.0 (RC)
Reporter: Garrett Conaty
Priority: Blocker
Fix For: 2.0
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.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
