[
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?
|
Adding new options by default is not that hard. Lets hope only those are the restrictions.
Thanks
Sravan
-----Original Message-----
From: cross-project-issues-dev <cross-project-issues-dev-bounces@xxxxxxxxxxx> On Behalf Of Stephan Herrmann via cross-project-issues-dev
Sent: Thursday, July 11, 2024 4:09 AM
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Cc: Stephan Herrmann <stephan.herrmann@xxxxxxxxx>
Subject: [EXTERNAL] 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
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
