Fork me on GitHub
#boot
<
2018-08-08
>
miikka08:08:01

Should BOOT_JVM_OPTIONS work? I have this in my boot.properties and I still get erased stack traces.

BOOT_CLOJURE_NAME=org.clojure/clojure
BOOT_CLOJURE_VERSION=1.9.0
BOOT_VERSION=2.8.1
BOOT_JVM_OPTIONS=-XX:-OmitStackTraceInFastThrow

borkdude09:08:59

I have -XX:-OmitStackTraceInFastThrow as well, but you might want to check if it doesn’t get overridden in your project

miikka11:08:51

That's my project's boot.properties

seancorfield16:08:31

Pretty sure you can't override JVM options in boot.properties -- after all, the JVM is already running by the time that file is read in to start Boot.

seancorfield16:08:57

^ @miikka @borkdude

dominicm17:08:30

Hmm, that's probably true then, @miikka what is boot -v ran from your home directory? You might need to boot -u

dominicm17:08:00

that's not right, I meant to dump out the version

dominicm17:08:08

boot --version

borkdude17:08:30

oh yeah, I have a script that sets BOOT_JVM_OPTIONS, it’s not in my boot.properties

dominicm17:08:24

@miikka boot -u should make that work

seancorfield18:08:14

Wouldn't the Boot "core" file need to be updated for that change in 2.8.1 to take effect?

dominicm18:08:52

is that not what boot -u does?

seancorfield18:08:33

@dominicm I thought that only updated boot.properties which then caused the JAR files to be updated (but not the runner itself).

seancorfield18:08:08

Looks like the boot.sh file hasn't changed so I'm clearly wrong about that 😐

dominicm18:08:32

@seancorfield you might be right, I've run boot -u, and can't get boot to pick up the jvm_options I'm setting.

dominicm18:08:47

yeah, boot-bin needs a release

seancorfield18:08:28

OK, good. So I'm not crazy after all :exploding_head: