[ http://jira.codehaus.org/browse/MNG-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170620#action_170620 ]
Brett Porter commented on MNG-4093: ----------------------------------- it won't update SNAPSHOT if you have timestamped artifacts on the remote repository. You need to choose. In the local repository, as long as your maven-metadata-local.xml is intact you should get the correct version (the timestamp, or the local one if set by useLocalCopy because you installed it via mvn install) > SNAPSHOT jars not correctly updated > ----------------------------------- > > Key: MNG-4093 > URL: http://jira.codehaus.org/browse/MNG-4093 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies > Affects Versions: 2.0.10 > Reporter: Gin-Ting Chen > > Occasionally I would get compilation errors after releasing a new SNAPSHOT > dependency of a project. > After some debugging I found that it was adding a -SNAPSHOT.jar to my > classpath and not the actual timestamped jar. > But I also found that, occasionally, I would get this: > {code} > -rw-r--r-- 1 tich tich 1482491 common-util-25-20090313.151759-9.jar > -rw-r--r-- 1 tich tich 1482490 common-util-25-20090317.001243-13.jar > -rw-r--r-- 1 tich tich 1482491 common-util-25-SNAPSHOT.jar > {code} > It seems that the SNAPSHOT downloading process *silently* fails to update the > x-SNAPSHOT.jar. > This behavior seems to occur randomly and can not be recovered from until you: > * delete the corrupted local repository OR > * release a new snapshot -- 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