Fork me on GitHub
#babashka
<
2022-06-10
>
jose09:06:56

I'm trying to build the babashka uberjar with tools.build, but I get an error:

Execution error (ExceptionInfo) at clojure.tools.namespace.dependency.MapDependencyGraph/depend (dependency.cljc:88).
Circular dependency between babashka.impl.protocols and babashka.impl.protocols
Do you know how to fix it? I'm looking to the current build setup, but I don't get how leiningen solves the circular dependency issue

dmegas14:06:42

Does anyone know if clj-kondo is available as a library in bb?

dmegas15:06:00

Thank you very much, I'll give it a go!

cldwalker15:06:43

When pulling in tasks via a dependency, is it possible to also pull in the pods they use? It doesn't seem so but figure I'd ask. https://github.com/logseq/bb-tasks has tasks for clj-kondo and fswatcher pods that would benefit from this behavior

borkdude15:06:31

Hey! That library looks good. Currently the pods aren't pulled in, not sure how to do that yet, but worth creating an issue for. As a workaround you could also use load-pod in your tasks

borkdude15:06:42

An outcome of this issue could in fact be that you should still use load-pod for library code

borkdude15:06:52

Not sure how to get data declared in other deps into bb but perhaps the clojure.basis file works for that

borkdude15:06:02

Anyway, this has to be investigated

cldwalker15:06:32

I'm hoping to only have pod versions in deps.edn but workaround makes sense. This is not a major inconvenience right now but one day perhaps it will be for more of the community if pods usage increases. Happy to make an issue to see if others are interested in this

👍 1