Fork me on GitHub
#leiningen
<
2019-05-06
>
plexus13:05:30

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)

plexus13:05:19

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

alexmiller13:05:15

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.

plexus14:05:47

thanks, I'll see what I can find... seems it doesn't happen when AOT is disabled

alexmiller14:05:43

it was something to do with which directories were getting included

plexus14:05:53

this seems to be the same or a similar issue: https://github.com/bhauman/figwheel-main/issues/134

alexmiller14:05:31

target is where .class output goes so could be aot-specific

plexus14:05:44

taking "target" out of :resource-paths now, I'm guessing that will fix it

plexus14:05:25

just migrated this project to figwheel-main, which must've been why I added target there

plexus14:05:39

yay, it worked 🙂 thanks @alexmiller