Did you see if the artifact in the repo has an incorrect checksum deployed to the repo? There are a couple of repos that did not enforce checksum validation/repair... And maven 2.1.0 through 2.2.0 deploy incorrect checksums to remote repos (which is why we say don't use those versions)
On Thursday, 7 June 2012, DK wrote: > I'm getting a number of errors in my build like the following: > > *** CHECKSUM FAILED - Checksum failed on download: local = > '2b0cd22fcfe2c88328b8c30eb57bc24b4b20ed'; remote = > '746e3c8abfad7fdc3d6384dd1a9b6b448140ef' - RETRYING > *** CHECKSUM FAILED - Checksum failed on download: local = > '2b0cd22fcfe2c88328b8c30e7c1bc24b4b20ed'; remote = > '746e3c8abfad703fdc6384dd1a9b6b448140ef' - IGNORING > > Anyone know the cause? The error doesn't appear to be affect the build > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Maven-clean-install-throws-Checksum-failed-on-download-tp5710934.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] <javascript:;> > For additional commands, e-mail: [email protected]<javascript:;> > >
