[
http://jira.codehaus.org/browse/MNG-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91127
]
Micah Whitacre commented on MNG-1142:
-------------------------------------
This issue is also occurring when I am not excluding the upper bound of the
version range. As an example I have a dependency on which I use the range
[3,3.3], it always resolves to try and find the version 3.3 even though that
version does not exist in any of the repositories I have listed.
> restriction of [1.6,) and [1.5,1.6.2) in that order results in 1.6.2 instead
> of 1.6.1
> -------------------------------------------------------------------------------------
>
> Key: MNG-1142
> URL: http://jira.codehaus.org/browse/MNG-1142
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Reporter: Brett Porter
> Priority: Minor
> Fix For: 2.1.x
>
>
> 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.
--
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
