[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] JNI is here to stay, isn't it?
|
Am 10.07.24 um 19:07 schrieb Aleksandar Kurtakov:
On Wed, Jul 10, 2024 at 7:04 PM SRAVAN LAKKIMSETTI <sravankumarl@xxxxxxxxxx
<mailto:sravankumarl@xxxxxxxxxx>> wrote:
[...] > For now we will need to add --enable-native-access=ALL-UNNAMED by default in
the eclipse launcher/ini file.
that shouldn't be hard, should it?
Adding the new arg wouldn't even be necessary in the first stage, but hopefully
improve compatibility with future Java versions, where it may become required.
@Aleksandar Kurtakov @loskutov@xxxxxx <mailto:loskutov@xxxxxx> Any comments
on this one?
Are the changes in Java 24 ea builds already? I can't really comment before
getting hands dirty to understand the details.
The current discussion around
https://mail.openjdk.org/pipermail/jdk-dev/2024-July/009222.html is whether or
not JEP 472 shall target Java 24.
Any implementation changes should only be expected after that decision.
Remember that the upcoming release is still Java 23 :)
You may want to keep an eye on https://bugs.openjdk.org/browse/JDK-8307341 ...
best,
Stephan
