Sounds like a bug to me... On 17/05/2007, at 9:02 AM, Mark Hobson wrote:
Hi there, I'm working on tests for MRELEASE-177 which has led me to investigate how ranges are resolved. An example problem was [1.0,2.0] resolving to 2.0 irrespective of the repository metadata. This appears to be due to VersionRange.getSelectedVersion and isSelectedVersionKnown which selects the upper bound if present and inclusive. DefaultArtifactCollector then blindly uses this without consulting the artifact metadata. Any idea why VersionRange special cases this situation? All the integration tests pass without it. Cheers, Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
