I know this is really late to be mentioning this, but would it be possible to mark a site as unreachable for the duration of a build once it can't be reached the first time? Then, continual failure on the same site for multiple dependencies wouldn't be such a problem...of course, you wouldn't want to mark it unreachable if you received a 404...
Anyway, just food for thought. -john On Sun, 2004-02-15 at 21:30, Brett Porter wrote: > I'll take it for a spin when I get a chance with a current CVS build of > Maven so it should all be right to go with Maven RC2 when it is released. > I'll come over to directory-dev and chat if I have any Q's. > > Cheers, > Brett > > > -----Original Message----- > > From: Alex Karasulu [mailto:[EMAIL PROTECTED] > > Sent: Monday, 16 February 2004 1:28 PM > > To: 'Maven Users List' > > Subject: RE: Maven b10 hangs on some jars > > > > > > Yeah unfortunately it blew chunks when I tried it w/ rc1. > > But I found a > > way to work around the delay just fine on b10. You were > > right on about > > the server being the issue. It was just shocking to see it > > hanging over > > and over again on the same darn jars. Thought I was going mad. I > > created and use my own temp repo and maven runs like a champion now. > > > > Thanks, > > Alex > > -- John Casey [EMAIL PROTECTED] CommonJava Open Components Project http://www.commonjava.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
