-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Native Image] --enable-native-access
does not work for JPMS module
#10489
Labels
Comments
(Invoking with |
Appending
|
sgammon
changed the title
[Native Image]
[Native Image] Jan 15, 2025
--enable-native-access
does not work for entrypoint JPMS module--enable-native-access
does not work for JPMS module
See branch |
cc / #8113 This issue disappears on the latest GVM EA Java 25 release:
The warning also disappears. |
If I am not mistaken this is fixed by #10076 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Issue
(1) Building a
jar
with amodule-info.class
present that has amain-class
should work(2) Additionally, identifying that entrypoint module within
--enable-native-access=...
should allow native accessUsing the latest version of GraalVM can resolve many issues.
GraalVM Version
Operating System and Version
Linux CALVIN 5.15.167.4-microsoft-standard-WSL2 #1 SMP Tue Nov 5 00:21:55 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Build Command
Expected Behavior
Comparing with the JVM command:
I expected the output:
Actual Behavior
Invoking the native image instead produces:
Steps to Reproduce
make
Additional Context
No response
Build Log Output and Error Messages
The text was updated successfully, but these errors were encountered: