Maven complains about a checksum failure for several SLF4J logging jars. I removed the SLF4J stuff in my local repository and temporarily removed a reference to a local caching maven mirror, thinking that it was a temporary glitch. But it's still complaining. For example:
Downloading: http://repo1.maven.org/maven2/org/slf4j/slf4j-log4j12/1.0.1/slf4j-log4j12-1.0.1.pom 406b downloaded [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '37304fd56d9cdda797718e6710637d232986c442'; remote = '15558150f0136e9802bb95a347e0045fb4ffe697' - RETRYING Downloading: http://repo1.maven.org/maven2/org/slf4j/slf4j-log4j12/1.0.1/slf4j-log4j12-1.0.1.pom 406b downloaded [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '37304fd56d9cdda797718e6710637d232986c442'; remote = '15558150f0136e9802bb95a347e0045fb4ffe697' - IGNORING How might I proceed to investigate this problem? It's easy to ignore this problem but I don't have a good conscience doing so. By the way... without maven implicitly checking the checksum and reporting a problem to me, I don't know how to manually check the checksum for myself. -- View this message in context: http://www.nabble.com/Investigating-a-checksum-failure-tf2142454.html#a5914017 Sent from the Maven - Users forum at Nabble.com.
