[
http://jira.codehaus.org/browse/MNG-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-2988:
-------------------------------
>From Mark's email:
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.
> Ranges with inclusive upper bounds are not validated against metadata
> ---------------------------------------------------------------------
>
> Key: MNG-2988
> URL: http://jira.codehaus.org/browse/MNG-2988
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.6
> Reporter: Mark Hobson
> Assignee: Brett Porter
> Fix For: 2.0.7
>
> Attachments: patch.txt
>
>
> See http://www.mail-archive.com/[EMAIL PROTECTED]/msg67131.html
> Patch attached.
--
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
