RFR: 8327218: Add an ability to specify modules which should have native access enabled [v2]
Jan Lahoda
jlahoda at openjdk.org
Tue Mar 5 12:44:10 UTC 2024
On Tue, 5 Mar 2024 12:41:18 GMT, Jan Lahoda <jlahoda at openjdk.org> wrote:
>> Currently, JDK modules load by the bootstrap and platform ClassLoaders are automatically granted the native access. I am working on an upgrade of JLine inside the `jdk.internal.le` module, and I would like to replace the current native bindings with FFM-based bindings (which are now somewhat provided by JLine). But, for that, native access is needed for the `jdk.internal.le` module. We could possibly move the module to the platform ClassLoader, but it seems it might be better to have more control over which modules have the native access.
>>
>> This patch introduces an explicit list of modules that will automatically be granted the native access. Note this patch is not yet intended to change the end behavior - the list of modules granted native access is supposed to be the same as modules in the boot and platform ClassLoaders.
>
> Jan Lahoda has updated the pull request incrementally with one additional commit since the last revision:
>
> Apply suggestions from code review
>
> Co-authored-by: ExE Boss <3889017+ExE-Boss at users.noreply.github.com>
> Co-authored-by: Maurizio Cimadamore <54672762+mcimadamore at users.noreply.github.com>
src/java.base/share/classes/jdk/internal/module/ModuleBootstrap.java line 806:
> 804: /**
> 805: * Process the --enable-native-access option to grant access to restricted methods to selected modules.
> 806: * Also add Enable native access from JDK modules.
Suggestion:
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/18106#discussion_r1512761636
More information about the core-libs-dev
mailing list