This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-12-21
Channels
- # adventofcode (27)
- # announcements (2)
- # babashka (1)
- # beginners (111)
- # calva (11)
- # cider (82)
- # clara (6)
- # clojure (44)
- # clojure-dev (5)
- # clojure-europe (27)
- # clojure-nl (5)
- # clojure-spec (3)
- # clojure-uk (3)
- # clojurescript (29)
- # core-async (5)
- # cursive (4)
- # datalevin (1)
- # datomic (39)
- # exercism (4)
- # figwheel-main (1)
- # fulcro (32)
- # graalvm (7)
- # gratitude (1)
- # integrant (4)
- # jobs (1)
- # lein-figwheel (3)
- # leiningen (4)
- # lsp (3)
- # luminus (3)
- # meander (2)
- # nextjournal (1)
- # off-topic (10)
- # other-languages (26)
- # pathom (14)
- # polylith (9)
- # re-frame (16)
- # remote-jobs (1)
- # shadow-cljs (4)
- # specter (2)
- # sql (6)
- # timbre (2)
- # tools-build (12)
- # xtdb (9)
Anyone using https://github.com/liquidz/antq or similar with polylith ? be interested in an example alias seems antq is no longer happy since I refactored into polylith style
We use antq
at work and we tell it which directories to check for deps.edn
. I'll drop the example code into this thread for folks who are interested.
clojure -Sdeps '{:deps {com.github.liquidz/antq {:mvn/version "RELEASE"}}}' -M -m antq.core \
--skip=pom \
--error-format="| {{name}} | {{version}} | {{latest-version}} |" \
--reporter=format -d .:`ls -d * bases/* components/* projects/* | tr '\n' ':'` 2> /dev/null | sort -u
That finds the top-level deps.edn
(via .
), our legacy subproject format (via *
), and then Polylith's bricks and projects.
okay grand thanks @U04V70XH6 will give that a try
I copied my alias from my root folder into my project folder but I now get greeted with this "var: #'clojure.tools.deps.alpha.util.maven/get-settings is not public"
We use antq
at work and we tell it which directories to check for deps.edn
. I'll drop the example code into this thread for folks who are interested.
there should be support for that in 1.3.0 https://github.com/liquidz/antq/issues/115
so you can point it at a top level project and it will crawl through your components deps
With the caveat that it doesn't know about projects
and any additional deps those might bring in that are not covered by your workspace deps.edn
and the components reachable from it.