Issue 1528: enable native access to silence JNA warning on Java 25+ - #194
Merged
Conversation
Appends --enable-native-access=ALL-UNNAMED to JAVA_ADD_OPENS in entrypoint.sh, same fix as install-script's JAVA_REFLECTION_JAR_OPS for the containerized launch path.
2 tasks
labkey-gokhano
approved these changes
Aug 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale
JNA, pulled in transitively by docker-java for the docker module, calls System.load, which JEP 472 flags as a restricted method starting around Java 24 and warns about under Java 25 unless native access is explicitly enabled. Adds --enable-native-access=ALL-UNNAMED to entrypoint.sh's JAVA_ADD_OPENS so the warning no longer appears in container logs.
Related to https://github.com/LabKey/kanban/issues/1528
Related Pull Requests
Changes