You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2009/12/16 11:41:55 UTC
[jira] Created: (MNG-4498) Don't fail dependency resolution if one
remote repo's metadata is broken
Don't fail dependency resolution if one remote repo's metadata is broken
------------------------------------------------------------------------
Key: MNG-4498
URL: http://jira.codehaus.org/browse/MNG-4498
Project: Maven 2 & 3
Issue Type: Improvement
Components: Artifacts and Repositories
Affects Versions: 3.0-alpha-5, 2.2.1
Reporter: Benjamin Bentmann
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).
--
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
[jira] Closed: (MNG-4498) Don't fail dependency resolution if one
remote repo's metadata is broken
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4498.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0-alpha-6
Assignee: Benjamin Bentmann
Improved in [r891200|http://svn.apache.org/viewvc?view=revision&revision=891200].
> Don't fail dependency resolution if one remote repo's metadata is broken
> ------------------------------------------------------------------------
>
> Key: MNG-4498
> URL: http://jira.codehaus.org/browse/MNG-4498
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1, 3.0-alpha-5
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-6
>
>
> 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).
--
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