Hey! Thanks for the awesome work on babashka!
I'm trying to port some internal tooling to it. Currently the tool integrates with projects as a lein profile which loads a dependency. invoked using lein run -m xxx
.
Right now I set BABASHKA_CLASSPATH
using lein classpath
, but that boots an entire jvm to calculate the classpath.
Is there a faster / other recommended way? Thanks
@jeroen.dejong what do you need on the babashka classpath? only directories?
or also jar / gitlibs?
The tool lives on a private maven repository, including some deps indeed.
To add deps to the bb classpath from maven, you can use babashka.deps (brand new): https://book.babashka.org/#babashkadeps
this comes with 0.2.5
it will invoke java once for calculating the classpath but after that its cached
That seems great! The caching with clj -Sdeps
works neatly, so i'm stoked. Already on 2.5 so I'll give it a spin!
Thanks
it's using the same tools.jar as the official Clojure CLI, just a different "front-end" so to speak. babashka also supports --clojure
as an alternative CLI to the official Clojure CLI for invoking a JVM Clojure
bb --clojure -Spath
for exampleAll our projects are on leiningen right now, but it's just 1 dependency for the tool. I think finding the right deps according to the nearest project.clj should be doable 🙂
Yeah, sure, parsing a project.clj ain't that hard