jline triggers a restricted method warning on modern JVMs
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start with the :repl alias and the clojure-cli.repl.server entry point, then trace how the spawned client receives JVM options. Reproduce the warning on JDK 27 and verify that --enable-native-access=ALL-UNNAMED reaches the client and removes the JLine warning.
Written by the indexing model from the issue text.
Description
[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+.
- Dominant language
- Clojure
- Stars
- 20
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from clojure/clojure-cli.repl
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
clojure/clojure-cli.repl#6 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
clojure/clojure-cli.repl#5 · 1 reaction ·
All issues in clojure/clojure-cli.repl
Similar issues
-
.Needs Triage .Team/UXWest Priority:P2 Type:Bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
metabase/metabase#83998 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
clojure-emacs/cider-nrepl#1053 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
bhauman/clojure-mcp-light#34 ·