This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-29
Channels
- # aleph (4)
- # architecture (12)
- # bangalore-clj (1)
- # beginners (87)
- # boot (3)
- # cider (19)
- # cljs-dev (84)
- # clojars (10)
- # clojure (79)
- # clojure-italy (7)
- # clojure-nl (19)
- # clojure-russia (10)
- # clojure-spec (9)
- # clojure-uk (55)
- # clojurescript (64)
- # core-async (7)
- # core-typed (4)
- # cursive (7)
- # data-science (2)
- # datomic (8)
- # devcards (6)
- # docs (1)
- # duct (5)
- # fulcro (117)
- # graphql (1)
- # instaparse (1)
- # leiningen (13)
- # lumo (103)
- # nyc (3)
- # off-topic (54)
- # om (9)
- # onyx (1)
- # pedestal (6)
- # planck (3)
- # portkey (7)
- # re-frame (26)
- # reagent (20)
- # ring-swagger (14)
- # shadow-cljs (164)
- # sql (11)
- # tools-deps (25)
- # yada (1)
it seems like the jvm-opts from project.clj don’t get set when running a ‘lein deploy’ command
does that sound right and is there another option i should be setting?
running into module errors when trying to do a ‘lein deploy’ with java 9
@nickmbailey makes sense I’d expect :jvm-opts
to only be set in environments that run your app code
yeah i also agree that makes sense
but java 9 makes things weird with the modules system
and the s3-wagon-private plugin apparently needs the xml.bind module
which is easy enough but i need a way to pass that to the jvm doing the deploy
maybe not but java 10 would have the same issue
i suppose i can use java8 for deploying for now and file a github issue
looks like there’s LEIN_JVM_OPTS