[edited, now that I understand more of how the CLI REPL works and the handling of aliases in tools.deps/create-basis]
Running the CLI REPL on JDK 27 yields this warning:
WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::load has been called by org.jline.nativ.JLineNativeLoader in an unnamed module (file:/home/sean/.m2/repository/org/jline/jline/4.3.1/jline-4.3.1.jar)
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module
WARNING: Restricted methods will be blocked in a future release unless native access is enabled
The client needs to have this added to the alias (:attach):
:jvm-opts ["--enable-native-access=ALL-UNNAMED"]
If you have an :attach alias in your deps.edn file, per this project's README, you can add that line and it will solve it for clojure -M:attach (as expected).
Because of the way aliases defined in multiple sources (root, user, project, extra, via -Sdeps) are handled when a basis is created, the way that the CLI REPL server starts the client (for the :repl alias) will pick up the :jvm-opts from your deps.edn file!
That is because alias definitions are merged across sources, per this Ask about aliases and sources.
As long as that behavior does not change, adding the :jvm-opts shown above to the :attach alias in deps.edn is sufficient. If that behavior changes—or users create a different alias for starting the client (@practicalli-johnny this applies to you since you used a different name in your config!)—then the server code will need updating to add the :jvm-opts when spawning the client.
I think the safest approach is to update the server code to add that, since it works on JDK17+.
[edited, now that I understand more of how the CLI REPL works and the handling of aliases in
tools.deps/create-basis]Running the CLI REPL on JDK 27 yields this warning:
The client needs to have this added to the alias (
:attach):If you have an
:attachalias in yourdeps.ednfile, per this project's README, you can add that line and it will solve it forclojure -M:attach(as expected).Because of the way aliases defined in multiple sources (root, user, project, extra, via
-Sdeps) are handled when a basis is created, the way that the CLI REPL server starts the client (for the:replalias) will pick up the:jvm-optsfrom yourdeps.ednfile!That is because alias definitions are merged across sources, per this Ask about aliases and sources.
As long as that behavior does not change, adding the
:jvm-optsshown above to the:attachalias indeps.ednis sufficient. If that behavior changes—or users create a different alias for starting the client (@practicalli-johnny this applies to you since you used a different name in your config!)—then the server code will need updating to add the:jvm-optswhen spawning the client.I think the safest approach is to update the server code to add that, since it works on JDK17+.