Benjamin Bentmann wrote: > Hi, > > considering the recent fixes to checksums for stuff in central, I was > wondering what's the overall state of (existing) checksums on central > these days? > > Assuming checksums are correct where present, this should put us in a > good position to introduce a new checksum policy "fail-if-present" or > just "strict" some day. The difference to the existing "fail" policy > would be to only fail the build if at least one checksum file to verify > is actually present. Making this policy the default for central would > reduce the grief caused by Maven happily downloading HTTP status pages > and trying to build class paths from HTML files... > > > Benjamin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
I just ran into this issue of download http error pages as artifacts last week, so I would welcome a more strict default checksum policy. For fixing the checksums currently in central, can we just run a script to regenerate md5 and sha1 files? This is what I did for the JBoss repo. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
