[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[cross-project-issues-dev] JNI is here to stay, isn't it?
|
Hi folks,
Two things are happening in the area of interfacing Java with native code:
In JDK 22 a new technology called FFM API has matured to a standard
feature [1].
In JDK 24 a process is started to *restrict* the use of JNI [2]. See
this recent announcement [3].
While both topics are somehow related, the current strategy does not
imply that JNI will be removed in a foreseeable future, but the
*default* may eventually be shifted towards disabling JNI by default,
which means at that point you'll need to supply a new command line arg
to the java launcher to enable JNI. This is intended to ensure
"integrity by default".
If some proposed changes could potentially break any part of Eclipse,
then it would certainly be good to speak up sooner rather than later.
Right now, however, I don't see any action required. I just think it's
good to keep everybody informed.
best,
Stephan
[1] https://openjdk.org/jeps/454
[2] https://openjdk.org/jeps/472
[3] https://mail.openjdk.org/pipermail/jdk-dev/2024-July/009222.html
