You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2008/07/09 23:51:27 UTC
[jira] Updated: (MNG-2994) Snapshot repositories are not checked
when using ranges
[ http://jira.codehaus.org/browse/MNG-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MNG-2994:
----------------------------
Fix Version/s: (was: 2.0.10)
2.0.11
This will need to wait until the other snapshots-in-version-ranges issue (referenced as a prerequisite for this issue) is resolved. Otherwise, we risk changing existing build behavior for version ranges in very bad ways.
> Snapshot repositories are not checked when using ranges
> -------------------------------------------------------
>
> Key: MNG-2994
> URL: http://jira.codehaus.org/browse/MNG-2994
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.6
> Environment: Windows XP, Cygwin
> Reporter: Mark Hobson
> Assignee: Jason van Zyl
> Fix For: 2.0.11
>
> Attachments: MNG-2994-2.patch, MNG-2994-3.patch, MNG-2994-core-it.patch, patch.txt
>
>
> The attached patch demonstrates the problem by adding it0121. If the test repository has releases enabled, the test passes, when they are disabled, the test fails. This appears to be due to DefaultArtifact.isSnapshot returning false for unresolved ranges, thus causing snapshot repositories to be disabled when resolving artifacts.
--
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