This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-04
Channels
- # admin-announcements (9)
- # beginners (40)
- # boot (61)
- # cider (6)
- # cljsrn (5)
- # clojure (65)
- # clojure-gamedev (6)
- # clojure-greece (8)
- # clojure-ireland (1)
- # clojure-portugal (5)
- # clojure-russia (46)
- # clojure-uk (38)
- # clojurescript (177)
- # core-async (9)
- # cursive (17)
- # datomic (6)
- # dirac (8)
- # emacs (5)
- # error-message-catalog (8)
- # hoplon (248)
- # ldnclj (11)
- # ldnproclodo (1)
- # lein-figwheel (36)
- # leiningen (12)
- # mount (2)
- # off-topic (3)
- # om (26)
- # onyx (12)
- # perun (2)
- # planck (26)
- # re-frame (62)
- # reagent (55)
- # remote-jobs (2)
- # rethinkdb (1)
- # ring-swagger (14)
- # spacemacs (47)
- # untangled (69)
Hey all, is there a way to resolve the problem of having 2 dependencies in a project.clj
that themselves have a dependency in common but w/ incompatible versions?
if I include dep C explicitly then the version is wrong for either A or B, depending on which version of C I include.
@ccann: http://stackoverflow.com/questions/35328825/issues-with-clojure-inter-dependency-with-different-major-versions-of-the-same-l/35329118#35329118
I ended up dealing with the issue by factoring out part of the program into a separate one, which was an option in this case
Fundamentally it’s just a really big problem
aka Diamond Dependency Problem