JEP draft: Prepare to Restrict The Use of JNI

[Alex Buckley]

On 8/28/2023 5:40 PM, Ryan Schmitt wrote:
> If JNI is going to be /de facto/ deprecated, it's reasonable for Java
> developers to wonder how their needs will be met without it.
I know what you mean by "/de facto/ deprecated", but let's not speak in 
a way that can cause confusion. JNI is not being deprecated _in any 
way_. There is no plan to remove JNI now or in the future.

We're proposing that JNI receives exactly the same treatment as the 
foreign-function parts of the FFM API (see 
https://openjdk.org/jeps/8307341#Risks-and-Assumptions). That treatment 
is: disabled by default, enabled by the user.

Alex