Rob Browning <r...@defaultvalue.org> writes:
> From a preliminary investigation, it looks like this is being caused by
> a maven-resolver version that's too old. The class mentioned,
> NoopNamedLockFactory, doesn't appear to have been added until 1.7.0,
> while Debian has 1.6.3.
I thought I'd seen that unstable also had 1.6.3, but it has 1.9.22, so
that's not it.
As Jérôme Charaoui pointed out, there's a new jar
(maven-resolver-named-locks.jar) that contains the class, and that we
need to add to run-build-tests.
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"}))
--
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
