[MNG-1908] snapshots not deployed using m2, or deployed with uniqueVersion = false are not updated if present locally

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.0.1
• Fix Version/s: 2.0.5
• Component/s: Artifacts and Repositories
• Assignee: Brett Porter
• Reporter: Guillaume Nodet
• Created: 02/Jan/06 03:37
• Updated: 30/Jul/10 13:59
• Resolved: 03/Apr/07 17:22

Description

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.

Issue Links

• is duplicated by: MNG-2289 Newer SNAPSHOT parents in the remote repository are ignored
• is duplicated by: MNG-2601 mvn -U does NOT update/download the latest SNAPSHOT version
• is duplicated by: MNG-1919 If deploy with uniqueVersion=false (only generate file ended SNAPSHOT), this is not downloaded
• is related to: MNG-3144 Snapshots not updated when using uniqueVersion false
• relates to: MNG-2780 snapshots are not updated based on metadata deployed with uniqueVersion = false
• relates to: MNG-2790 lastUpdated timestamp in local repository metadata not updated on install if it already exists
• relates to: MNG-3137 IT 0108 (snapshot updates) fail intermittently