On 12/8/06, Christian Goetze <[EMAIL PROTECTED]> wrote:
I am using the maven proxy as described in
http://docs.codehaus.org/display/MAVENUSER/Using+Maven+in+a+corporate+environment,
but I am observing spurious build failures due to some of the actual
remote sites not always responding in a timely manner.
Is there a way to configure maven proxy to not fail, but to simply send
the cached version instead? Should I just set the cache timeout to some
really large value? What I would like, though, is that it does try to
get an update, but not fail if the update fails?
Can you paste in the types of build failures you are getting?
I haven't looked in our logs for a long time.
Having a quick browse I am seeing
2006-12-07 16:31:43,168 [WARN ] commons.httpclient.HttpMethodBase -
Error getting URI host
org.apache.commons.httpclient.HttpException: Redirect from host
www.ibiblio.org to mirrors.ibiblio.org is not supported
at
org.apache.commons.httpclient.HttpMethodBase.checkValidRedirect(HttpMethodBase.java:1237)
at
org.apache.commons.httpclient.HttpMethodBase.processRedirectResponse(HttpMethodBase.java:1185)
But my builds are still working...
Archiva will eventually superced mvn-proxy. But Archiva isn't ready
for general use yet.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
