This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-06
Channels
- # announcements (3)
- # aws (23)
- # beginners (61)
- # calva (57)
- # cider (121)
- # clara (1)
- # clj-kondo (9)
- # cljs-dev (62)
- # cljsrn (3)
- # clojure (79)
- # clojure-europe (2)
- # clojure-nl (19)
- # clojure-spec (9)
- # clojure-uk (14)
- # clojurescript (92)
- # clojureverse-ops (2)
- # cursive (3)
- # data-science (2)
- # duct (1)
- # figwheel (2)
- # graphql (6)
- # jobs (1)
- # kaocha (5)
- # leiningen (11)
- # off-topic (25)
- # overtone (1)
- # pedestal (4)
- # portkey (1)
- # re-frame (1)
- # remote-jobs (2)
- # shadow-cljs (179)
- # slack-help (3)
- # specter (7)
- # testing (14)
- # tools-deps (14)
- # unrepl (12)
- # vim (2)
- # yada (3)
I'm having an issue where doing lein jar
or lein uberjar
on a project never finishes, but instead creates a jar that just keeps getting bigger indefinitely (I've let it run up to 40GB, whereas the resulting jar should only be 100MB)
anyone ever seen such a thing? I have no idea how to start debugging this... I also can't see what Leiningen is stuffing in there, because when I interrupt it the result is not a valid jar/zip
something similar to this was discussed in recent past, maybe in #leiningen - something like recursively including the results of the jar process in the jar? I don't remember the details.
it was something to do with which directories were getting included
this seems to be the same or a similar issue: https://github.com/bhauman/figwheel-main/issues/134
target is where .class output goes so could be aot-specific
just migrated this project to figwheel-main, which must've been why I added target
there
yay, it worked 🙂 thanks @alexmiller