Hi Maven users, Does anyone know why slf4j-jcl-1.0.1's checksum is invalid in Maven Central?
I'm investigating the following warning message: [WARNING] Could not validate integrity of download from https://repo1.maven.org/maven2/org/slf4j/slf4j-jcl/1.0.1/slf4j-jcl-1.0.1.pom: Checksum validation failed, expected 7035ae7774a9a082a316a6943bbad9dfab6319b3 but is c5c0a3fff6071a4c720f1b7aa1b66cb9d0b26a21 When I checked https://repo1.maven.org/maven2/org/slf4j/slf4j-jcl/1.0.1/slf4j-jcl-1.0.1.pom.sha1, it has 7035ae7774a9a082a316a6943bbad9dfab6319b3 /home/projects/maven/repository-staging/to-ibiblio/maven2/org/slf4j/slf4j-jcl/1.0.1/slf4j-jcl-1.0.1.pom However, curl and sha1sum say otherwise: suztomo@suztomo:~/spring-cloud-gcp$ curl https://repo1.maven.org/maven2/org/slf4j/slf4j-jcl/1.0.1/slf4j-jcl-1.0.1.pom |sha1sum % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 394 100 394 0 0 4061 0 --:--:-- --:--:-- --:--:-- 4104 c5c0a3fff6071a4c720f1b7aa1b66cb9d0b26a21 - So from my perspective, the discrepancy is in line with the Maven warning message. Maven Central is hosting invalid checksum files. Does anyone know why this discrepancy happens slf4j-jcl-1.0.1? -- Regards, Tomo
