This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-05
Channels
- # beginners (29)
- # boot (29)
- # cider (54)
- # cljs-dev (99)
- # cljsjs (31)
- # cljsrn (39)
- # clojars (32)
- # clojure (171)
- # clojure-austin (2)
- # clojure-berlin (5)
- # clojure-brasil (3)
- # clojure-greece (2)
- # clojure-italy (1)
- # clojure-korea (11)
- # clojure-spec (202)
- # clojure-uk (166)
- # clojurescript (130)
- # cursive (54)
- # datomic (99)
- # dirac (18)
- # figwheel (6)
- # hoplon (23)
- # lambdaisland (3)
- # leiningen (8)
- # luminus (14)
- # off-topic (11)
- # om (3)
- # om-next (24)
- # onyx (59)
- # planck (25)
- # protorepl (10)
- # re-frame (49)
- # reagent (14)
- # ring-swagger (2)
- # rum (46)
- # schema (1)
- # slack-help (6)
- # specter (7)
- # testing (7)
- # untangled (115)
- # yada (1)
@jerger_at_dda not 100% sure I understand what you're trying to do, but have you looked at Leiningen's new managed dependencies features?
Not exactly.
I'm searching for a way to use [lib-dep "1.0.0"] in myclient without re-compile & install / deploy of liba.
If I understand the FAQ https://github.com/technomancy/leiningen/blob/master/doc/FAQ.md correct, it should be enought, to define client as follows: (defproject myclient :dependencies [[lib-dep "1.0.0"] [liba]]). Is this correct?
I think leiningen would use the more recent lib-dep, but you can also just do [liba :exclusions [lib-dep]]
to avoid pulling in the older version
Unfortunately your assumption is wrong, I traced this in some cases in very detail (to get the idea there are wrong versions involved took me some hours ... ). The mentioned FAQ says "The decision depends on which depth and which order the dependencies come in the :dependencies vector" - but I did not figure out, which kind of order is the right one. Exclusions are working fine, but having more than 10 exclusions will get unhandy also ...