[ http://jira.codehaus.org/browse/MNG-1908?page=comments#action_75302 ] Adam Lewis commented on MNG-1908: ---------------------------------
I have a similar problem. The artifacts are deployed using m2, the metadata on the repo is generated. When I do a build, maven logs that it has found a snapshot version and is checking for updates. It downloads and updates my local metadata for that repo, but DOES NOT download the updated JAR. THIS IS A BLOCKING ISSUE. If a release is not planned soon, the fix needs to be back ported. Having snapshots that don't update reduces the usefullness of SNAPSHOT to ZERO. Actually its worse than that, because we expect that SNAPSHOTS be updated from our internal repo and maven behaves as if it is updating them and then it does NOTHING. A fix in 2.1 does nothing for us if 2.1 doesn't get releases soon. > snapshots not deployed using m2, or deployed with uniqueVersion = false are > not updated if present locally > ---------------------------------------------------------------------------------------------------------- > > Key: MNG-1908 > URL: http://jira.codehaus.org/browse/MNG-1908 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories > Affects Versions: 2.0.1 > Reporter: Guillaume Nodet > Assigned To: Brett Porter > Priority: Blocker > Fix For: 2.1 > > Original Estimate: 30 minutes > Time Spent: 2 hours, 30 minutes > Remaining Estimate: 0 minutes > > It seems from the log info that m2 is trying to locate the artifact metadata > on the repository. > SInce this artifact has been generated from m1, there is no metadata. > So whatever repository settings are configured, m2 will never update snapsots. -- 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
