You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Benedict (JIRA)" <ji...@codehaus.org> on 2014/07/02 15:44:42 UTC

[jira] (MNG-3132) New SNAPSHOT versions on (self managed) remote repository are downloaded but not used

     [ https://jira.codehaus.org/browse/MNG-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Benedict updated MNG-3132:
-------------------------------

    Fix Version/s:     (was: Issues to be reviewed for 3.x)

> New SNAPSHOT versions on (self managed) remote repository are downloaded but not used
> -------------------------------------------------------------------------------------
>
>                 Key: MNG-3132
>                 URL: https://jira.codehaus.org/browse/MNG-3132
>             Project: Maven
>          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 was sent by Atlassian JIRA
(v6.1.6#6162)