Rob Browning <r...@defaultvalue.org> writes:
> With that, most of the tests succeed, but there's one failure in
> deploy-artifacts due to missing .asc.HASH files.
>
> FAIL in (deploy-artifacts) (aether_test.clj:337)
> Should deploy correctly demo "1.0.0"
> expected: (= #{"demo-1.0.0.pom.md5" "demo-1.0.0.jar.sha1"
> "demo-1.0.0.pom.asc.sha1" "demo-1.0.0.pom.asc.md5" "demo-1.0.0.jar"
> "demo-1.0.0.pom.sha1" "demo-1.0.0.pom.asc" "demo-1.0.0.jar.md5"
> "demo-1.0.0.jar.asc.md5" "demo-1.0.0.jar.asc.sha1" "demo-1.0.0.pom"
> "demo-1.0.0.jar.asc"} (set (.list (io/file tmp-remote-repo-dir "demo" "demo"
> "1.0.0"))))
> actual: (not (= #{"demo-1.0.0.pom.md5" "demo-1.0.0.jar.sha1"
> "demo-1.0.0.pom.asc.sha1" "demo-1.0.0.pom.asc.md5" "demo-1.0.0.jar"
> "demo-1.0.0.pom.sha1" "demo-1.0.0.pom.asc" "demo-1.0.0.jar.md5"
> "demo-1.0.0.jar.asc.md5" "demo-1.0.0.jar.asc.sha1" "demo-1.0.0.pom"
> "demo-1.0.0.jar.asc"} #{"demo-1.0.0.pom.md5" "demo-1.0.0.jar.sha1"
> "demo-1.0.0.jar" "demo-1.0.0.pom.sha1" "demo-1.0.0.pom.asc"
> "demo-1.0.0.jar.md5" "demo-1.0.0.pom" "demo-1.0.0.jar.asc"}))
After a bit more digging, it looks like this may be due to a change in
aether's handling of aether.checksums.forSignature /
aether.checksums.omitChecksumsForExtensions, which it then looks like
pomegranate upstream handled in
1f010c691a232fb0b986f79f8294bedd86c45938.
Upgrading to 1.2.23 or newer may fix the problem.
cf.
https://maven.apache.org/components/resolver-archives/resolver-LATEST-1.x/configuration.html
https://maven.apache.org/components/resolver-archives/resolver-1.9.22/configuration.html
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
