You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/05/16 07:27:34 UTC

[jira] Closed: (MAVEN-1163) mark remote repo with failed (not 404) download as unavailable

     [ http://jira.codehaus.org/browse/MAVEN-1163?page=all ]
     
Brett Porter closed MAVEN-1163:
-------------------------------

    Resolution: Won't Fix

ctrl-C, edit build.properties, try again :)
In the event that it was an intermittent error, the current technique is actually better.

> mark remote repo with failed (not 404) download as unavailable
> --------------------------------------------------------------
>
>          Key: MAVEN-1163
>          URL: http://jira.codehaus.org/browse/MAVEN-1163
>      Project: maven
>         Type: Improvement
>   Components: core
>     Versions: 1.0-rc2
>  Environment: all
>     Reporter: John Casey
>     Priority: Minor

>
> Original Estimate: 2 hours
>         Remaining: 2 hours
>
> 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...

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org