This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-10-01
Channels
- # announcements (8)
- # aws (8)
- # babashka (21)
- # beginners (125)
- # calva (12)
- # cider (10)
- # circleci (29)
- # clara (6)
- # clj-kondo (34)
- # cljdoc (3)
- # cljfx (65)
- # cljs-dev (18)
- # clojure (38)
- # clojure-australia (4)
- # clojure-berlin (5)
- # clojure-czech (2)
- # clojure-dev (15)
- # clojure-europe (22)
- # clojure-nl (3)
- # clojure-uk (31)
- # clojuredesign-podcast (7)
- # clojurescript (87)
- # code-reviews (1)
- # conjure (3)
- # cursive (2)
- # data-science (1)
- # datalog (1)
- # datomic (36)
- # emacs (12)
- # events (1)
- # fulcro (3)
- # graalvm (68)
- # instaparse (2)
- # jackdaw (2)
- # jobs (2)
- # leiningen (8)
- # luminus (2)
- # nrepl (31)
- # pedestal (44)
- # releases (1)
- # remote-jobs (6)
- # shadow-cljs (4)
- # spacemacs (4)
- # sql (13)
- # tools-deps (56)
- # uncomplicate (4)
- # xtdb (40)
- # yada (11)
Could someone explain me what’s the meaning of sentences like the one below, displayed by leiningen, when running lein :deps
Tried to load org.jsoup/jsoup version 1.13.1 but 1.11.3 was already loaded.
@viebel coming from this:
# leiningen.core.classpath/warn-conflicts
"When using the bootclasspath (for boot speed), resources already on the
bootclasspath cannot be overridden by plugins, so notify the user about it."
I believeso any way it is trying to come in otherwise is being disregarded - meaning the bootclasspath one version is the one that is used
this is how I interpret it - not famliiar with seeing this issue come up for me personally though.
looks like perhaps this warning has been pushed to :pendantic?
mode only now https://github.com/technomancy/leiningen/commit/1a502050c7c0bdb95f1da2382a8ec64ccde74e36