[MNG-3415] Transfer errors cause junk metadata in the local repo

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.8
• Fix Version/s: 2.0.9
• Component/s: Artifacts and Repositories
• Assignee: John Dennis Casey
• Reporter: Brian E Fox
• Created: 21/Feb/08 08:59
• Updated: 10/Mar/16 13:54
• Resolved: 10/Mar/08 12:41

Description

I see this all the time and I swear there was an issue for it, but now I can't find it. Sometimes there is metadata in the repo, usually after an offline build or a build where something went wrong downloading artifacts. Maven will apparently decide based on the metadata that the file can never be found and will simply fail on a missing artifact. You can tell this has happened because no attempt has actually been made to download the artifact from a repository. Subsequent clearing of (portions) the localrepo fixes the issue. This is terribly confusing to new users...and annoying to everyone.

Issue Links

• duplicates: MNG-3399 Maven shows fake network error until the next updatePolicy period
• is duplicated by: MNG-2941 Sometime SNAPSHOTs can not be downloaded in an an online build
• is related to: MNG-1320 Build failed due to an empty or corrupt metadata file in the repository
• is related to: MNG-2712 update policy 'daily' not honored
• is related to: MNG-3312 Maven creates empty plugin metadata during offline mode, causing successive online builds to fail
• relates to: MNG-3411 got the error like(Searching repository for plugin with prefix: 'archetype',repository is black listed,The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exits)