This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-06-10
Channels
- # announcements (1)
- # babashka-sci-dev (16)
- # beginners (5)
- # calva (3)
- # cider (42)
- # clojure (103)
- # clojure-europe (79)
- # clojure-nl (2)
- # clojure-norway (17)
- # clojure-sweden (2)
- # clojure-uk (8)
- # clojurescript (7)
- # community-development (7)
- # core-async (1)
- # core-typed (18)
- # cursive (9)
- # data-science (1)
- # dev-tooling (14)
- # events (1)
- # fulcro (2)
- # hugsql (2)
- # hyperfiddle (1)
- # leiningen (7)
- # malli (11)
- # re-frame (14)
- # releases (9)
- # ring (18)
- # shadow-cljs (55)
My project uses leiningen and deps.edn together. The bridge being lein-tools-deps
plugin. I am trying to use #flow-storm (clojure-strom) that requires us to exclude the org.clojure/clojure
dependency altogether and use its "instrumentation enabled" fork.
lein-tools-deps
flattens the deps tree and then resolves the dependencies. This is adding clojure as a dependency even after it's been added to :exclusions
at the top level.
How can I exclude clojure
as a dependency here?
https://clojurians.slack.com/archives/C03KZ3XT0CF/p1717994731626399?thread_ts=1697986872.473769&cid=C03KZ3XT0CF
looking at the https://github.com/RickMoynihan/lein-tools-deps it starts with :
Do you really want to use this?
Probably not, it has been over 4 years since its last update; and is hugely behind on changes in tools.deps. If you think you need to use this, then you should expect to fork it and maintain it going forward, or if you require git/deps use tools.build instead.
@U05AJ7KNDGE out of curiosity, what is the reason you currently use a plugin like that?
I think there are lein plugins specifically for that