You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Pavel Halas (JIRA)" <ji...@codehaus.org> on 2007/04/18 16:13:46 UTC
[jira] Issue Comment Edited: (MNG-2839) Non-unique-version
snapshots not updated
[ http://jira.codehaus.org/browse/MNG-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93312 ]
Pavel Halas edited comment on MNG-2839 at 4/18/07 9:13 AM:
-----------------------------------------------------------
Yes. It's the hardcore use case. Nevertheless, it fails to update it (without such manual changes) in regular update cycle (based on settings.xml) too.
was:
Yes. It's the hardcore use case. Nevertheless, it fails to update it in regular update cycle (based on settings.xml) too.
> Non-unique-version snapshots not updated
> ----------------------------------------
>
> Key: MNG-2839
> URL: http://jira.codehaus.org/browse/MNG-2839
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.5
> Reporter: Pavel Halas
>
> Test case:
> - let's have a repository with [uniqueVersion]false[/uniqueVersion].
> - let your project download any snapshot dependency (with non-unique version) (like abc-1.0-SNAPSHOT.jar).
> - go to your local repository and change the file content. You can also remove all the metadata.
> - run "mvn -U" on your project
> - you get "[INFO] snapshot abc:abc-1.0-SNAPSHOT: checking for updates from YOUR-REPOSITORY"
> - the abc-1.0-SNAPSHOT.jar in your local repository is NOT updated.
> The same (I think) bug has been reported (and closed) several times before (MNG-1908 etc.) but it still appears in 2.0.5.
--
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