there is no way to provide a global jvm opt

you can provide them in an alias with :jvm-opts as you have above and then use the alias

{:aliases {:snoop {:jvm-opts ["-Dsnoop.enabled"]}}}

clj -A:snoop

thanks! I'm sure there has to be a reason for that, but I don't see it at first glance

do you happen to have any insight on why that has to be the case?

most jvm options don't make sense for the open world of all possible programs you might run in a project

so I'm not terribly convinced yet that this is a good feature to have :)

I see, thank you! 🙂

I've just added some pages on JVM options, showing how to use them with Clojure CLI. https://practical.li/clojure/reference/clojure-cli/jvm-options.html There are also a number of examples and https://practical.li/clojure/reference/jvm/java-17-flags.html. There are a lot of options to choose from 🙂 It would be very interesting to know which options are commonly used. I've put together https://practical.li/clojure/reference/jvm/common-options.html. Appreciate any corrections if something is not quite right.

I would definitely add the OmitStackTrace one

-XX:-OmitStackTraceInFastThrow

That is the most common jvm option I use

And probably next most common are the —illegal-access flags - debug and deny

Interesting. It seems the --illegal-access flag was marked deprecated in Java 16, with https://openjdk.java.net/jeps/403. So maybe one day it will be less common :)

Well I missed that!

That's actually great, I'm glad they switched the default to deny as that means the reflection canAccess methods will actually work

The Clojure reflector uses that feedback to look further up the inheritance chain for a public method to call

Aren't server and tiered compilation on by default?