Greetings, On Thu, Jun 14, 2012 at 10:09 AM, Brett Porter <[email protected]> wrote: > Could you try with 3.0.3? The pre-emptive authentication might have an effect.
That didn't affect things. Using auto-installed Apache Maven 3.0.3 with invocation: mvn -e -U versions:display-dependency-updates versions:display-plugin-updates jenkins.build.log: [INFO] artifact org.apache.derby:derby: checking for updates from archiva [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '307a219b1200b6a5567a27c1f8b9d2158873ce1e'; remote = '13d4c724c1ea3fea0ce4d36fe1e0e99996565937' - RETRYING [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '307a219b1200b6a5567a27c1f8b9d2158873ce1e'; remote = '13d4c724c1ea3fea0ce4d36fe1e0e99996565937' - IGNORING archiva.log: 2012-06-14 12:36:55 all guest a.b.c.d "org/apache/derby/derby/maven-metadata.xml" "Modified File (proxied)" 2012-06-14 12:36:55 all guest a.b.c.d "org/apache/derby/derby/maven-metadata.xml" "Modified File (proxied)" 2012-06-14 12:36:56 all guest a.b.c.d "org/apache/derby/derby/maven-metadata.xml" "Created File (proxied)" 2012-06-14 12:36:58 all guest a.b.c.d "org/apache/derby/derby/maven-metadata.xml" "Modified File (proxied)" 2012-06-14 12:36:58 all guest a.b.c.d "org/apache/derby/derby/maven-metadata.xml" "Modified File (proxied)" 2012-06-14 12:36:59 all guest a.b.c.d "org/apache/derby/derby/maven-metadata.xml" "Modified File (proxied)" access.log: a.b.c.d - - [14/Jun/2012:12:36:56 -0400] "GET /repository/all/org/apache/derby/derby/maven-metadata.xml HTTP/1.1" 200 474 a.b.c.d - - [14/Jun/2012:12:36:57 -0400] "GET /repository/all/org/apache/derby/derby/maven-metadata.xml.sha1 HTTP/1.1" 200 64 a.b.c.d - - [14/Jun/2012:12:36:59 -0400] "GET /repository/all/org/apache/derby/derby/maven-metadata.xml HTTP/1.1" 200 474 a.b.c.d - - [14/Jun/2012:12:37:00 -0400] "GET /repository/all/org/apache/derby/derby/maven-metadata.xml.sha1 HTTP/1.1" 200 64 And some investigation into the various repositories and what we have as hashes: ~/data/repositories> find | grep 'org/apache/derby' | grep -v derby-project | grep -v derbyclient | grep metadata.xml.sha1 | while read sha ; do cat $sha ; echo " -- $sha" ; done | sort 35c8220539cf6241988387b428705cdc3f34c175 maven-metadata.xml -- ./repository-external-glassfish/org/apache/derby/derby/maven-metadata.xml.sha1 507fb5cd83e467361df8b770f6ff37af03810fd1 maven-metadata.xml -- ./repository-external-central/org/apache/derby/derby/maven-metadata.xml.sha1 896f95af918cc8b7e54ecd997ebb74a02095143d maven-metadata.xml -- ./repository-external-central/org/apache/derby/derby/10.8.2.2/maven-metadata.xml.sha1 896f95af918cc8b7e54ecd997ebb74a02095143d maven-metadata.xml -- ./repository-external-glassfish/org/apache/derby/derby/10.8.2.2/maven-metadata.xml.sha1 b71a91c0b4afa464112a4710dd2b0cf6ebb89f5b maven-metadata.xml -- ./repository-external-jenkins/org/apache/derby/derby/maven-metadata.xml.sha1 b7a6395e2316183ffeee6ae4c6f7c4e683414fd6 maven-metadata.xml -- ./repository-external-sonatype/org/apache/derby/derby/maven-metadata.xml.sha1 db141276ddfa81dfe05ee5bec342acdf3c244e40 maven-metadata.xml -- ./repository-external-central/org/apache/derby/derby/10.8.1.2/maven-metadata.xml.sha1 db141276ddfa81dfe05ee5bec342acdf3c244e40 maven-metadata.xml -- ./repository-external-glassfish/org/apache/derby/derby/10.8.1.2/maven-metadata.xml.sha1 db141276ddfa81dfe05ee5bec342acdf3c244e40 maven-metadata.xml -- ./repository-external-sonatype/org/apache/derby/derby/10.8.1.2/maven-metadata.xml.sha1 So it's almost like one repository is used to provide the metadata and another is used to provide the artifact. The /repository/all is just a list of all repositories defined. I think this is really slowing my builds down, in addition to clogging up the logs, .. please let me know what I can do to help resolve this faster. Thanks, -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not.
