[
http://jira.codehaus.org/browse/MRM-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137066#action_137066
]
Marc Lustig commented on MRM-798:
---------------------------------
Not quite. The use-case is not "unable to find artifact x on remote-repo y".
The use-case is "cannot connect to the remote-repo due to
server-unavailability".
The alterative would be to manually check every hour if all the remote repo's
that are configured are still available :-(
Ideal solution: custom cron-task to (asynchronously) check the availability of
all the remote repos.
Once a connect fails, the sys-admin should get an email-notification
"Warning: remote-repository y is currently down and has been locked! Unlock
repository [Link to page to unlock the locked repository]"
Please re-open. Ty.
> blacklisting unavailable remote reps
> ------------------------------------
>
> Key: MRM-798
> URL: http://jira.codehaus.org/browse/MRM-798
> Project: Archiva
> Issue Type: Improvement
> Components: repository interface
> Affects Versions: 1.0.2
> Reporter: Marc Lustig
> Assignee: Brett Porter
>
> once one of the repos configured as a proxy-connector is down, the mvn
> build-process slows down extremely as the connect time-out is about 1 minute
> (for each repo and each artifact).
> There should be a configuration available to adjust blacklisting repos that
> have been identified as non-reachable.
> Such repos should be able to get re-avtivated manually.
--
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
