Hi Andreas and Kristiyan, Cc’ing Roman and Rostislav who are among the recent committers for this file.
Andreas Bauer <[email protected]> wrote: > Now it can be fixed with time machine: > > guix time-machine --commit=98e4bfe96f2c99daa0b66b65c1d379bb385301a8 -- guix > shell --pure --development --check clojure-tools openjdk coreutils > > Then in time-machine run again clojure-X:curl and the demo will work. Kristiyan Kanchev <[email protected]> skribis: > I'm seeing issues with the project Metabase: > https://github.com/metabase/metabase. When `clojure -M:run`, it fails with: > Execution error (ClassNotFoundException) at java.net.URLClassLoader/findClass > (URLClassLoader.java:476). > jakarta.servlet.AsyncContext > > The problem seems to be that Clojure CLI (`clojure-tools` guix package) > doesn't construct proper class path including all transitive > dependencies of the project. I've tried to figure out what might be causing > the issue and I suspect `maven-resolver-*` packages. Clojure > CLI depends on `tools.deps` clojure lib, which itself depends on > `maven-resolver-*`. There is a mention in the `tools.deps` changelog of > reverting `maven-resolver-*` libs in version 0.18.1374 with comment "Revert > update of Maven resolver libs - seeing resolution > differences". > Here is the relevant commit: > https://github.com/clojure/tools.deps/commit/04539cd060d41a528794c04b50a6aa2293b672ce > > Up until this date, `tools.deps` lists the older versions of maven-resolver-* > libs in its deps.end file. Since Guix uses the latest versions of > maven-resolver-* libs, I think this is causing the issue. Roman, Rostislav: does that ring a bell? Thanks, Ludo’.
