Why on earth are you depending on the network at all?  We have our build
locked down by using an  internal mirror of central + custom snapshots.
Anything else is non-deterministic and then management starts asking
questions...

-----Original Message-----
From: Daniel Kulp [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 17, 2006 8:03 PM
To: dev@maven.apache.org
Cc: Brett Porter; Carlos Sanchez
Subject: Re: rsync-ability for maven-snapshot-repository on apache?


Brett,

> This is the main concern. We should be cutting releases this week, and

> fewer people using the snapshots off of Apache.
>
> I'm curious why a maven-proxy in the middle doesn't alleviate this 
> issue for you.

The maven-proxy doesn't help much on Monday mornings.   The rest of the 
week it's OK.   We have the timeout for snapshots set at 48 hours.   If 
no-one does anything over the weekend (and this was a holiday weekend so

no-one did), then the caches are pretty much moot on Monday.   

It was kind of amusing (not) this morning when we all came in.   There 
were four of us trying to build and each of our builds were failing at 
different spots.   Each would get a little bit further.   All while 
trying to check the snapshot server.     By the afternoon, we were
pretty 
much all set, but I really don't want this to happen everyweek (or on
Wednesday when the timeouts from today start expiring).

We used to have the same problem with ibiblio (and even the mirrors) so
we started rsyncing ibiblio local.  Now we don't have problems with
that, just the apache snapshot server.  (the codehaus snapshot server is
much better behaved)

Thanks!
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727  C: 508-380-7194
[EMAIL PROTECTED]

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



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

Reply via email to