[ http://jira.codehaus.org/browse/MNG-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-3604. ----------------------------- Resolution: Won't Fix it uses the metadata in the local repository. the current defined behaviour is to honour manually installed artifacts, unless the remote one is newer. i believe there is an open issue to review this for the future already, but for now it is by design. > when team member installs after deploy, snapshot is not updated > --------------------------------------------------------------- > > Key: MNG-3604 > URL: http://jira.codehaus.org/browse/MNG-3604 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies > Affects Versions: 2.0.x > Environment: Win XP > Reporter: bartvdc > Priority: Minor > > I deployed a project A with a snapshot version and a team member did not get > the update when he builds another project B that has this project A as > dependency, not even with -U . We found out that it was because he did an > install of the same project A after I deployed it. He had not changed > anything, so the version part did not change. > On the repo we had a -20080516... and in his local repo there was a > -20080514... file. > Apparently Maven does not look at the file names(the -20080516... part) but > keeps the install time elsewhere. > If the deployed file comes before the the install time, no update is done. > The project must be deleted in his local repo to get the latest 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