This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-07-08
Channels
- # announcements (2)
- # babashka (100)
- # beginners (25)
- # biff (7)
- # calva (13)
- # cider (24)
- # clj-kondo (39)
- # cljsrn (2)
- # clojure (22)
- # clojure-dev (13)
- # clojure-europe (12)
- # clojure-gamedev (3)
- # clojure-losangeles (2)
- # clojure-nl (1)
- # clojure-norway (3)
- # clojure-spec (11)
- # clojure-uk (2)
- # clojurescript (20)
- # core-async (8)
- # cursive (7)
- # data-science (2)
- # datomic (14)
- # emacs (6)
- # events (7)
- # fulcro (9)
- # honeysql (1)
- # kaocha (24)
- # lambdaisland (3)
- # leiningen (6)
- # lsp (30)
- # membrane (7)
- # missionary (10)
- # nbb (48)
- # nextjournal (13)
- # off-topic (6)
- # parinfer (4)
- # pathom (1)
- # polylith (1)
- # reagent (7)
- # rewrite-clj (6)
- # ring (11)
- # sci (7)
- # shadow-cljs (8)
- # sql (13)
Hi folks. When lein calculates the classpath, is there anything special about dev
dependencies?
To be more precise: I’d like to add a dev dependency to my project, but I don’t want its transitive dependencies to override the ones calculated by the main dependencies.
That is, I’d like to transitive dependencies from dev
to always have a slower priority, so the classpath used using dev time is as close as possible to the one used in prod.
There's nothing special about dev (other than that it's being activated by default).
However any given profile is more specific that the 'base' dependencies of a project map, which is why they're taking priority.
I think the standard approach is to use :pedantic?
so that conflicting transitive deps are reported as such.
Sometimes :pedantic?
in dev is very annoying, but it might be sound to run it in CI as a 'linter' of sorts.
Actually, it would be added to a lein profile. I suppose the logic is the same, still.