[
http://jira.codehaus.org/browse/MNG-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99623
]
Pavel Halas edited comment on MNG-2839 at 6/15/07 10:45 AM:
------------------------------------------------------------
Sample projects.
How to use it:
- deploy the dep1 project into a repository with non-unique version setup.
- work with the test project (like c:/temp/test/> mvn package)
- change the local repository content of the dep1-1.0-SNAPSHOT.jar
- enforce updating the dependencies (like c:/temp/test/> mvn package -U)
- check the dep1-1.0-SNAPSHOT.jar local repository content. Sometimes the
remote repository version is not used.
was:
Sample projects.
> Non-unique-version snapshots not updated
> ----------------------------------------
>
> Key: MNG-2839
> URL: http://jira.codehaus.org/browse/MNG-2839
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.5
> Reporter: Pavel Halas
> Assignee: Brett Porter
> Fix For: 2.0.x
>
> Attachments: dep-update.zip
>
>
> 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
