Persisted checksums written outside of the coursier cache
Persisted checksums were added in
2.0.5. These could mistakenly be written outside of the coursier cache, under
~/.ivy2/local for example. This release fixes that.
Changing artifacts in
cs get command
cs get command allows to download things via the coursier cache:
$ cs get https://repo1.maven.org/maven2/io/get-coursier/coursier-cli_2.12/maven-metadata.xml ~/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/io/get-coursier/coursier-cli_2.12/maven-metadata.xml
If a URL it is passed ends with
cs get should assume the artifact is changing (and may check for updates if the last check is older than the TTL). This release includes a fix for that. Prior to it, these were not assumed to be changing, so were not checked for updates.