mirror of https://github.com/sbt/sbt.git
7bf60557d9
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. |
||
|---|---|---|
| librarymanagement | ||
| project | ||
| .gitignore | ||
| .java-version | ||
| .scalafmt.conf | ||
| .travis.yml | ||
| README.md | ||
| build.sbt | ||
| sbt-allsources.sh | ||
README.md
librarymanagement module for sbt
git clone --no-hardlinks --branch 0.13 sbt sbt-modules/librarymanagement
cd sbt-modules/librarymanagement
git filter-branch --index-filter 'git rm --cached -qr -- . && git reset -q $GIT_COMMIT -- ivy util/cross' --prune-empty
git reset --hard
git gc --aggressive
git prune
git cb 1.0