Maven 2.2.0 has a bug that causes it to incorrectly calculate the outgoing checksums when deploying to an authenticated repository. (it doubles the stream and hashes that). You can repair this with the repair maven metadata command in Nexus.... then switch your build system to use 2.2.1 to stop it from producing new files with bad metadata.
2009/10/14 David Meunier <david.meun...@si4g.fr>: > Hi, I don't understand why this warning appears every time Maven downloads an Artifact from my remote Maven repository to my local repository. > > Downloading: https://www.si4g.fr/nexus/content/repositories/open4g-releases/com/open4g/open4g-parent/44/open4g-parent-44.pom > 9K downloaded (open4g-parent-44.pom) > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'ade3e7dcdc135bce55e1433d9ecd4724ef26e861'; remote = '8c75f4759f0ce6f4a5cc5839bb3931ff384a9448' - RETRYING > Downloading: https://www.si4g.fr/nexus/content/repositories/open4g-releases/com/open4g/open4g-parent/44/open4g-parent-44.pom > 9K downloaded (open4g-parent-44.pom) > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'ade3e7dcdc135bce55e1433d9ecd4724ef26e861'; remote = '8c75f4759f0ce6f4a5cc5839bb3931ff384a9448' - IGNORING > > - My Artifacts are released with Maven 2.2.0 and deployed to my Nexus repository (Linux Ubuntu Server). > - My local execution environment is Maven 2.2.1 on Windows XP. > > Can anyone tell me more about this please ? > > Best regards, > David Meunier. > >
