[MNG-4891] Improve robustness of snapshot dependency resolution in case a remote repo accidently uses the id "local"

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0
• Fix Version/s: 3.0.1
• Component/s: Artifacts and Repositories
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 09/Nov/10 05:20
• Updated: 09/Nov/10 06:32
• Resolved: 09/Nov/10 06:32

Description

This is a follow-up to MNG-4418. The model/settings validation that has been put in place to avoid metadata corruption of the local repo by a remote repo that misuses the same id doesn't help when plugins create repository instances on their own as with the maven-deploy-plugin in combination with its altDeploymentRepository parameter.

Using such a setup, the JGit folks ended up with builds that weren't able to resolve local snapshots that had just been installed seconds before. We need to improve the diagnostic output to more easily detect this kind of metadata corruption and gracefully recover from it.

Issue Links

• is related to: MNG-4418 Dependency resolution appears to misbehave if a remote repository uses the id "local"