[MNG-4498] Don't fail dependency resolution if one remote repo's metadata is broken

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.1, 3.0-alpha-5
• Fix Version/s: 3.0-alpha-6
• Component/s: Artifacts and Repositories
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 16/Dec/09 04:41
• Updated: 16/Sep/10 07:13
• Resolved: 16/Dec/09 05:34

Description

It can happen that Maven fetches broken maven-metadata.xml into the local repo (e.g. because it doesn't understand HTTP error codes properly and downloads HTML files or just because the remote repo serves crap). Currently, the bad metadata file for one repo will make the entire dependency resolution fail, regardless whether the repo/metadata in question is actually needed to complete the resolution.

We should just warn in case of unreadable metadata. If it was crucial for the current artifact resolution, it will still fail the build later on when all metadata has been merged (and the bits from the broken metadata are missing).

Issue Links

• is related to: MNG-2490 invalid remote repository metadata file installed in local repo
• relates to: MNG-4309 Checksum validation doesn't fail the build for repository metadata files