This is a followup to my message from Jan 8, about failing over to a
backup 'central' mirror when the primary mirror is down.
Wayne, the patch you directed me to at
http://jira.codehaus.org/browse/MNG-714 has indeed solved my problem and
allows me to fail over to a backup server. Endless
Hi everyone.
We had a seemingly random CruiseControl build failure today. When I
investigated, it appeared to have been caused by a fleeting error on our
local maven proxy server. Here's the snippet from maven-proxy.log:
2007-01-16 14:16:56,113 [INFO ] proxy.servlets.RepositoryServlet -
I just discovered a potentially important piece of information regarding
the IllegalStateException I saw on our maven-proxy server earlier today.
The jar in question did not have an associated pom file, meaning it was
probably originally uploaded manually uploaded by one of our developers,
not
Here is my current settings.xml:
mirror
idmirror/id
urlhttp://fawkes-dev01.ofoto.com:/repository/url
mirrorOfcentral/mirrorOf
/mirror
As you can see, I funnel all requests through our corporate maven proxy
mirror.
However, there is a SPOF. When fawkes-dev01 goes
I'm having trouble getting the correct format for the connectionURL
parameter to the mvn scm:tag command. Could anyone supply with me with
an example?
I'm following the examples at http://maven.apache.org/scm/perforce.html:
mvn -X -Dtag=foo4 -DconnectionUrl=scm:perforce:[EMAIL
