[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jdt-dev] Java 21 support for Eclipse 2023-09 (4.29)
|
Thanks for the correction concerning incubator modules. They are irrelevant for the compiler, but I should have named and described then correctly. My bad.
Am 7. Oktober 2023 13:51:38 GMT+07:00 schrieb Zheka Kozlov <orionllmain@xxxxxxxxx>:
There is no such thing as incubator features. There are only incubator modules. Incubator modules are not part of the Java SE platform. They are only candidates.
Hello everyone.
First, let me thank the JDT Core team for they tremendous effort and
impressive result. But...
Roland is right, despite any disclaimers in JDT Core release notes and
clarifications in another thread of this mailing list by Manoj Palat.
There is no such thing as "Java 21 Standard Features Support". If the
compiler wants to be Java 21 compatible, it needs to support preview and
incubator features, too. Imagine, you run it against a suite of
compatibility tests like this. It would simply fail. The preview and
incubator features are also specified by JEPs (i.e. "standard
features"), just like final language features and APIs.
I fully acknowledge that the dev team might be too busy and the time
line too tight to get it all done on time for the Open JDK 21 release
date, but please do not try to sell it as Java 21 support or as if
preview features were somehow second-class citizens. Just call the
release on the marketplace an alpha, milestone, preview or something
other suitable. It is not Java 21 compatible, if not all features are
covered.
P.S.: That you prioritise final language features over preview ones over
incubator ones, if completely understandable and the right thing to do.
But delivering those first, does not mean that the compiler is Java 21
compatible (yet).
Best regards
--
Alexander Kriegisch
https://scrum-master.de
Roland Grunberg via jdt-dev schrieb am 03.10.2023 22:01 (GMT +07:00):
> On Wed, 2023-09-20 at 06:01 +0000, Manoj Nalledathu Palat via jdt-dev
> wrote:
>> We are pleased to announce the Java 21 support for Eclipse 2023-09
>> (4.29).
>>
>> The release notably includes the support of the following standard
>> Java 21 features:
>>
>> [21] JEP 440: Record Patterns
>> [21] JEP 441: Pattern Matching for switch
>>
>> The release can be obtained through one of the following ways:
>>
>> 1. Java 21 Marketplace entry
>> : https://marketplace.eclipse.org/content/java-21-support-eclipse-202
>> 3-09-429
>> 2. P2 update site
>> : https://download.eclipse.org/eclipse/updates/4.29-P-builds/
>> 3. Additionally, the Java 21 support will be available on 4.29
>> from an integration build soon [tracked
>> viahttps://github.com/eclipse-jdt/eclipse.jdt.core/issues/1396] -
>> download from https://download.eclipse.org/eclipse/downloads/.
>>
>> The known issues and the preview features are retargeted to 4.30
>> timeframe or to the next Java version as appropriate.
>
> Thanks to everyone who worked on getting this out!
>
> For downstream consumers of the work done towards "Java 21 Support",
> are there any best practices/requirements around announcing this when
> some preview features are not yet complete ?
>
> Alex pointed me to https://openjdk.org/jeps/12 (regarding preview
> features) :
>
> "The desire for feedback and the expectation of quality means that
> these features are not "optional"; they must all be supported in full
> by every implementation of Java SE $N."
>
> That seems to imply we shouldn't declare it as "Java 21 Support". Has
> this happened before or is this a non-issue? Would the marketplace
> entry linked above be subject to this as well ?
>
> --
> Roland Grunberg
>
> _______________________________________________
> jdt-dev mailing list
> jdt-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jdt-dev
>
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev
