RFR: 8327218: Add an ability to specify modules which should have native access enabled [v4]

[Jan Lahoda]

On Thu, 7 Mar 2024 21:53:07 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:
> 
>   Adjusting javadoc as suggested.

Thanks for all the feedback and comments! I've filled:
https://bugs.openjdk.org/browse/JDK-8327686
to cover the cleanup of the modules with native access enabled, and:
https://bugs.openjdk.org/browse/JDK-8327688
to allow to configure the modules with native access at link time.

I can try to take a look at either of those, if desired.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/18106#issuecomment-1985530868