Closed l3nz closed 2 years ago
Hi, the issue seems to be caused by the fact that io.forward/yaml 1.0.10 was compiled with Java 11: binaries uploaded to Clojars are incompatible with Java 8. I tried to compile/install version 1.0.10 with Java 8: it works fine and even tests in presets_test.cljc
run smoothly.
I don't know how do you expect to fix this issue. Maybe we can stick with yaml 1.0.9 waiting for the author to release compatible binaries.
As @borkdude says it would be better to switch to [clj-commons/clj-yaml "0.7.0"]
- see https://github.com/l3nz/cli-matic/issues/113#issuecomment-1044668837
Worth trying, as next up will be a major release: https://github.com/clj-commons/clj-yaml
@l3nz Are you saying you are waiting for a major release of clj-yaml? Or do you mean something different?
@borkdude No I meant this will be a significant change so an incompatible library is kind-of OK
version
0.4.0 , JVM
problem
Updating to 1.0.10 breaks YAML tests.
repro
If we set:
[io.forward/yaml "1.0.9" :scope "provided"]
then test break, as in:
Of course we would like to detect EITHER versions.