matthiasblaesing commented on PR #7460: URL: https://github.com/apache/netbeans/pull/7460#issuecomment-2185331310
> the remaining question is should we set `--enable-native-access=ALL-UNNAMED` or not From my POV it would make sense to set it. It will most probably be necessary in the future anyway. If I understand the recent discussions on the openjdk mailinglists correctly, JNI loading will become restricted the same way as the foreign API (panama) and modules using JNI will need to be cleared the same way. To my understanding this will also affect JNA, which used JNI to load its FFI interface. The option is also guarded by the `-XX:+IgnoreUnrecognizedVMOptions` option (at least I deduce that from this): ```shell matthias@enterprise:~$ ~/bin/jdk-11/bin/java -XX:+IgnoreUnrecognizedVMOptions --enable-native-access=ALL-UNNAMED test.java Geht matthias@enterprise:~$ ~/bin/jdk-11/bin/java --enable-native-access=ALL-UNNAMED test.java Unrecognized option: --enable-native-access=ALL-UNNAMED Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. matthias@enterprise:~$ ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
