Improve robustness of snapshot dependency resolution in case a remote repo
accidently uses the id "local"
---------------------------------------------------------------------------------------------------------
Key: MNG-4891
URL: http://jira.codehaus.org/browse/MNG-4891
Project: Maven 2 & 3
Issue Type: Improvement
Components: Artifacts and Repositories
Affects Versions: 3.0
Reporter: Benjamin Bentmann
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.
--
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
