Fork me on GitHub
#boot
<
2016-10-07
>
lwhorton13:10:31

thanks @flyboarder I can never seem to remember the diff between asset resource and source đŸ˜•

flyboarder15:10:49

@lwhorton: it's documented on the wiki

alandipert19:10:35

@kenny i wanted to not aot every class, just one that the jar needs as entrypoint

alandipert19:10:04

just aot-ing the entrypoint and then using require/resolve to load in the rest of the app would have worked also

borkdude20:10:03

I wrote a script with a few functions that we need available in our boot.builds, before set-env! is called. Currently we load it with load-file. Is it possible to package this as a library/task somehow?

alandipert22:10:11

@borkdude you can always call set-env! multiple times

alandipert22:10:19

like at one point i made a library with a function that generated the argument to set-env!

alandipert22:10:57

so yeah, i'd make it a library per usual, and then just bring it in via set-env!/require before the next time you do set-env stuff

alandipert22:10:22

i believe the ability to do this subsumes e.g. maven archetype functionality

borkdude22:10:22

yes, that’s what I did too, a library to generate the argument for set-env

alandipert22:10:46

if you're making a jar or something in the consuming project, probably good to bring in your support lib w/ :scope test

alandipert22:10:08

alternatively you could make a pod at the top of yuor build.boot and load the library in there

alandipert22:10:12

then you're dep-conflict free

borkdude22:10:42

the library only uses native clojure