What does Error building classpath. The following libs must be prepared before use: [io.github.noahtheduke/lazytest] mean? does babashka expect clojure -T:prep before running?
This is just tools deps, not special to bb
if you have only one custom class, compiling it with the lowest bytecode version setting and just checking in the .class file into source control is worth preventing the prep-lib dance, imo
like we did here: https://github.com/nextjournal/markdown/tree/main/src/nextjournal/markdown/impl/types
e.g.:
javac --release 8 MyClass.javai mean my GH Action that calls bb lazytest raises this, which is surprising to me. i thought bb couldn't handle .class files: https://github.com/NoahTheDuke/lazytest/actions/runs/15940901952/job/44968809963#step:9:1
bb doesn't care about .class files, but if you specify in your library that it needs prepping, then tools.deps will require this
https://github.com/NoahTheDuke/lazytest/blob/1f3df317b36e7256513d955044be802e5d84bda3/deps.edn#L9
you can probably bypass this step by manually prepping the lib before you call bb
bb clojure -X:deps prepI don't know if it preps a local project though
it's silly to me that you have to prep deps with bb given it doesn't use the resulting class files lol
thanks, i got it working
I don't make tools.deps's rules
how did you get it working? I tried local prepping but I don't think the clojure CLI supports it
if tools.deps supports a toggle that avoids prepping, I'd happily use it
if you release a mvn/version we also don't have this problem with bb, so there's two ways to solve it currently
> I tried local prepping but I don't think the clojure CLI supports it
clojure -X:deps prep :current true maybe?
next release, #lazytest will support babaska! https://github.com/NoahTheDuke/lazytest/commit/9e1678956e105cf8b897885ed5262d57748731c3
hell yeah!
Added a little test for it too: https://github.com/babashka/babashka/commit/fc151ce361317636173917950fb9f7cb3f11e7cb Sometimes strange things happen in a native image with reflection (e.g. when some call returns some private class) so I usually add a smoke test like this
ah thanks, i should have written one
no worries
In 10 minutes or so you could use the dev build to run lazytest's tests in bb in CI I guess. I could also add them to bb's CI but the problem is, I'm using clojure.test, lol
amazing!
you're still going to the PR with the missing class, right?
(no hurry)
yes