This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-06-10
Channels
- # announcements (2)
- # aws (11)
- # babashka (11)
- # beginners (22)
- # calva (28)
- # cider (1)
- # clj-kondo (3)
- # clojars (14)
- # clojure (41)
- # clojure-europe (45)
- # clojure-norway (1)
- # clojure-uk (2)
- # clojured (31)
- # clojureindia (4)
- # cursive (5)
- # datahike (15)
- # datomic (11)
- # deps-new (11)
- # events (1)
- # holy-lambda (19)
- # introduce-yourself (1)
- # minecraft (17)
- # music (1)
- # nbb (3)
- # off-topic (37)
- # reagent (6)
- # reveal (3)
- # shadow-cljs (46)
- # tools-deps (8)
- # xtdb (22)
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 issueyou can call clj-kondo as a pod like this: https://github.com/borkdude/quickdoc/blob/362f065cf56e8ef341bbf91d2ff1ce02700eb87a/bb.edn#L1 https://github.com/borkdude/quickdoc/blob/362f065cf56e8ef341bbf91d2ff1ce02700eb87a/src/quickdoc/api.cljc#L6
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
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
An outcome of this issue could in fact be that you should still use load-pod
for library code
Not sure how to get data declared in other deps into bb but perhaps the clojure.basis file works for that