I think you simplified it a bit too much :-) Your version of the code now prints out an exception even on file not found on one repo but is available on others (although it does continue, which is good). (I hope it's obvious, but) you definitely do not want to do this in the multi-repo case; it's ok for the file to only be on one repo but not on others. In my usage for example, iBiblio is my main remote repo, but I have another 'local' remote repo that comes from CVS and supplies jars that aren't on ibiblio.


[EMAIL PROTECTED] wrote:

My bad, it wasn't. So I did something similar to the latest patches.
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au


[EMAIL PROTECTED] wrote on 10/02/2003 01:35:18 AM:


It looks like it has already been applied.
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au


Colin Sampaleanu <[EMAIL PROTECTED]> wrote on 10/02/2003 01:09:40 AM:


I think this one slipped by without being noticed.
http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-246
There is a second patch as my inline comment of Feb. 3 to properly handle failures with multiple remote repositories. Right now, if one
of
them goes down, you can't access any of the others, and there is no indication printed as to why there is a failure.

Colin Sampaleanu wrote:


Please reopen MAVEN-246 (additional patch supplied)
http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-246


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to