jvican 7bf60557d9 Implement `managedChecksums` in ivy ... Managed checksums tells ivy to forget about checking checksums for jar files and just persist them in the cache. The user that enables that option will take care of verifying they are correct. This is a big deal because: 1. Ivy takes *a lot of time* checking timestamps for big jars, and does it sequentially. The user (sbt) can do better by running these checks in parallel, speeding up the whole resolution process! 2. The fact that the sha files are not present in the cache means that build tools cannot check if a checksum is correct without preprocessing the jar. Note that the user is responsible for keeping the cache consistent. If the checksum is not correct, the user should report it and overwrite the checksum file with the valid digest.		2017-05-26 12:43:06 +02:00
..
src	Implement `managedChecksums` in ivy	2017-05-26 12:43:06 +02:00
NOTICE	Add build.sbt	2015-08-19 03:56:08 -04:00