The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Sat, 21 Feb 2004 7:37 PM
Changes:
Fix Version changed to 1.1
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1163&page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1163
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1163
Summary: mark remote repo with failed (not 404) download as unavailable
Type: Improvement
Status: Unassigned
Priority: Minor
Original Estimate: 2 hours
Time Spent: Unknown
Remaining: 2 hours
Project: maven
Components:
core
Fix Fors:
1.1
Versions:
1.0-rc2
Assignee:
Reporter: John Casey
Created: Mon, 16 Feb 2004 10:20 PM
Updated: Sat, 21 Feb 2004 7:37 PM
Environment: all
Description:
Currently, when you have multiple repo's, maven will always try each repo in order for
each dependency it attempts to download. This is not optimal behavior, and can easily
be improved by marking sites as unavailable upon the first failed dependency download.
This "marking" would only persist for the duration of the build, and would save the
[useless] retry of that site for successive dependencies.
Obviously, we wouldn't want to trigger the unavailable flag for 404's and the like...
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]