it isn't a new format, but wrong files. I fixed them. It can take few hours before they're available on ibiblio and mirrors.
Emmanuel Orjan Nygaard Austvold a écrit :
Hi, Today we have received a lot of POM validation failures due to checksum failure. I noticed that the content of md5 and sha1 files have changed to (e.g., commons-io-1.0) SHA1(commons-io/commons-io/1.0/commons-io-1.0.pom)= 901893f66d5b9de78c66dc39daebcb7569756666 This causes warnings such as Downloading: http://mirrors.sunsite.dk/maven2/commons-io/commons-io/1.0/commons-io-1.0.pom 5K downloaded [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '901893f66d5b9de78c66dc39daebcb7569756666'; remote = 'SHA1(commons-io/commons-io/1.0/commons-io-1.0.pom)=' - RETRYING Downloading: http://mirrors.sunsite.dk/maven2/commons-io/commons-io/1.0/commons-io-1.0.pom 5K downloaded [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '901893f66d5b9de78c66dc39daebcb7569756666'; remote = 'SHA1(commons-io/commons-io/1.0/commons-io-1.0.pom)=' - IGNORING [WARNING] POM for: 'commons-io:commons-io:pom:1.0' does not appear to be valid. Its will be ignored for artifact resolution. Reason: Failed to validate POM This seems also to be the reason why we cannot perform releases today. Needs to verify this first. Btw: continum for maven have complained about the same error to... :-) Thanks, Ørjan Austvold --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
