can we set jvm opts in environment variables to overcome this boot limitation?

@tmtwd Like BOOT_JVM_OPTIONS you mean?

(not sure what “limitation” you’re referring to)

stuff like -XX:+UseStringDeduplication

Anyone know how to get boot to 'compile' HugSQL queries into functions prior to building an uberjar? Is that even possible?

@pandeiro totally!

I have not yet done it, but a task could generate those for you using the HugSQL def-db-fns

Oh beautiful 🙂 Let me look that up

Thanks @flyboarder

the thing is that it’s designed to do those things at runtime, but you can do it at buildtime and generate a namespace with the resulting functions

Ah, it would have to generate a new namespace, not do it in place?

(new namespace + write file + add to fileset)?

yep

it’s mentioned on the intro https://www.hugsql.org/ but as runtime use

thats the best part of boot, you get an extra build layer to your clojure app, I use this to generate code

Boot->meta tasks->tasks->meta app->app

@pandeiro what I would do is use map-of-db-fns and then use the result of that as my list of forms for the generated namespace.

@flyboarder Very cool, yeah, the flexibility is the #1 reason to use boot IMO

For adzerk.boot-cljs, is it possible to set externs via task-options! or do I have to do it in my .cljs.edn file?

is there a way for the watch task to watch things that are external to the current project folder?

I saw a manual trigger but I never investigated how to actually trigger it