This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-31
Channels
- # announcements (5)
- # babashka (105)
- # beginners (92)
- # calva (77)
- # cider (17)
- # cljdoc (8)
- # cljs-dev (8)
- # cljsrn (8)
- # clojure (272)
- # clojure-dev (25)
- # clojure-europe (5)
- # clojure-italy (6)
- # clojure-nl (7)
- # clojure-norway (3)
- # clojure-uk (108)
- # clojurescript (326)
- # code-reviews (4)
- # cursive (6)
- # datomic (37)
- # duct (5)
- # emacs (14)
- # fulcro (23)
- # graphql (1)
- # juxt (1)
- # kaocha (2)
- # leiningen (10)
- # malli (9)
- # music (1)
- # nrepl (12)
- # pathom (21)
- # pedestal (2)
- # planck (4)
- # quil (3)
- # reitit (29)
- # rewrite-clj (10)
- # shadow-cljs (82)
- # spacemacs (29)
- # sql (6)
- # tools-deps (19)
without specifying any LEIN_JVM_OPTS
or equivalent, does lein
actually pass --illegal-access=permit
to java
by default?
so in https://github.com/technomancy/leiningen/blob/master/doc/MANAGED_DEPS.md#managed-dependencies it explains the goal is to > The idea is to provide a way to specify a version number for common library dependencies in a single location, and re-use those version numbers from other discrete maven/lein projects. But how does what you specify in :managed-depdencies do that? I can think of only one place. My ~/.lein/project.clj config that oversees "multiple projects" but thats just on a per computer basis. Is there a way for lein templates to build/reference each other in another way?
like can you point a lein project at a master project somewhere (a project.clj stored in s3) and it specifies these managed dependencies?
it seems the rest of the docs explain the answer lol
@drewverlee yeah a few plugins out there to do it in various ways.