I started to see the same thing recently, but not all the time. I need a closer look.
A couple of things to confirm: - is the checksum on disk correct (the .sha1 file in the archiva repository alongside the artifact)? - do you have the checksum correction consumer enabled or disabled? - is this repository proxying another, and if so, what is its checksum policy? This looks like it's on the maven-metadata.xml file for stax/stax-api, but it doesn't correlate to the one in the main maven repositories. Perhaps the metadata and its checksum are out of sync? Cheers, Brett On 14/06/2012, at 12:04 AM, Jesse Farinacci wrote: > Greetings, > > I am using Archiva 1.4-M2 via IBM Java 6 on Linux. During Jenkins > builds, I often see message blocks like: > > [INFO] artifact stax:stax-api: checking for updates from archiva > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '561b3c18354a1d64a198591ce93479fcc865ee48'; remote = > '6baba24f8e9bb17d12bb8b19623f21f4451e6147' - RETRYING > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '561b3c18354a1d64a198591ce93479fcc865ee48'; remote = > '6baba24f8e9bb17d12bb8b19623f21f4451e6147' - IGNORING > > This is most easily reproducible during a build which invokes: mvn -e > -U versions:display-dependency-updates versions:display-plugin-updates > > Does anyone have any advice on how to fix this? Thanks, > > -Jesse > > -- > There are 10 types of people in this world, those > that can read binary and those that can not. -- Brett Porter [email protected] http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter
