New SNAPSHOT versions on (self managed) remote repository are downloaded but
not used
-------------------------------------------------------------------------------------
Key: MNG-3132
URL: http://jira.codehaus.org/browse/MNG-3132
Project: Maven 2
Issue Type: Bug
Components: Dependencies
Affects Versions: 2.0.7
Reporter: Bryan Brouckaert
Attachments: BugReport.zip
I upload a new SNAPSHOT version to my self managed remote repository with the
"deploy:deploy-file" goal. The next maven run will download the new file into
the local repository, but the old version will still be used.
I included a test case (see attachment).
First, specify your self managed remote repository in the "pom.xml" and
"run.bat" files. Then execute the "run.bat" file, it should fail the second
time the test runs, but it doesn't because the old version is still used.
I did not check the code, but I did check the local repository. All files
seems to be normal (including 2 versions of the jar), except that the SNAPSHOT
version is still a copy of the first version while the meta files contain
information about the second version.
--
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
