Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.0.7
-
Component/s: Artifacts and Repositories
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
got this by adding ant [1.6,) to it0034, and ant [1.5,1.6.2) to one of its deps (deeper).
I think this is caused by the fact that versions are resolved too early instead of retaining the restriction, but it needs a further look.
from
MNG-1208Found while searching for
MNG-1207a call to VersionRange.getSelectedVersion() will return the upper bound even if the upper bound is exclusive. (and isSelectedVersionKnown would return false). This method should throw an exception if the selectedVersion is not known.
else
{
Restriction restriction = (Restriction) restrictions.get( restrictions.size() - 1 );
version = restriction.getUpperBound();
{ version = RELEASE; }if ( version == null )
}
MNG-1208Found while searching forMNG-1207a call to VersionRange.getSelectedVersion() will return the upper bound even if the upper bound is exclusive. (and isSelectedVersionKnown would return false). This method should throw an exception if the selectedVersion is not known. else { Restriction restriction = (Restriction) restrictions.get( restrictions.size() - 1 ); version = restriction.getUpperBound(); if ( version == null ) { version = RELEASE; } }