This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-17
Channels
- # beginners (52)
- # boot (116)
- # cider (21)
- # cljs-dev (44)
- # clojure (104)
- # clojure-dev (82)
- # clojure-greece (5)
- # clojure-japan (4)
- # clojure-nl (14)
- # clojure-russia (65)
- # clojure-serbia (3)
- # clojure-spec (38)
- # clojure-uk (9)
- # clojure-ukraine (1)
- # clojurescript (65)
- # clojurewest (1)
- # community-development (1)
- # core-logic (3)
- # cursive (5)
- # data-science (9)
- # datomic (13)
- # emacs (45)
- # euroclojure (1)
- # hoplon (2)
- # instaparse (23)
- # javascript (1)
- # jobs (2)
- # klipse (43)
- # leiningen (8)
- # lumo (25)
- # off-topic (7)
- # om (13)
- # om-next (3)
- # onyx (11)
- # pedestal (12)
- # planck (19)
- # proton (1)
- # re-frame (26)
- # reagent (26)
- # remote-jobs (13)
- # ring-swagger (23)
- # spacemacs (1)
- # untangled (3)
I’ve got a Pomegranate question. I’m attempting to use leiningen.core.classpath/get-dependencies to get a graph of all dependencies, including redundant ones
I’m trying to visualize dependencies but the normal code paths edit out common dependencies so that the graph makes it look like each shared dependency is only pointed to by one other dependency.
But I’m trying to see all the dependencies so I can identify what set of deps target other deps, and if there are version conflicts.
Looks like it takes some heavy work with Aether, in pedantic.core, to get at this data? Or is there something easier I can use?
… so again, if my project uses commons-codec, but also uses pedestal.service (which has a dependency on commons-codec), lein deps :tree
only sees the one dependency (from my project) and the normal dependency from pedestal.service to commons-codec is omitted. But I want to see that, so I can see all the ways a given dependency is included in my project, not just the first.
Hi, I just ran into what looks like https://github.com/cemerick/pomegranate/issues/71