On 01/05/2010, at 3:19 AM, 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?
Probably still not great. We aren't using these for an integrity-of-the-repository purpose, so perhaps it's a good time to automatically fix them on central (keeping a record of what was changed, and what it used to be just in case), then turn on the fail option by default. You can be sure if it fails by default that content will be more carefully managed :) > > 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] > -- Brett Porter [email protected] http://brettporter.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
