maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (MNG-4498) Don't fail dependency resolution if one remote repo's metadata is broken
Date Wed, 16 Dec 2009 10:41:55 GMT
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

        

Mime
View raw message