Eclipse 4.32 offers the execution environment JavaSE-23, although it is not yet supported

[howlger]

In the Eclipse SDK 4.32, in the New Java Project dialog, in the Use an execution environment JRE drop-down menu, JavaSE-23 is offered as an option, although it is not yet supported.

See also: #1349 (comment)

[akurtakov]

Running with JavaSE-23 EE is supported as this mandates the EE one wants to run with but it doesn't mandate that the bytecode generated from the project should be at level 23.
E.g. I can require using JavaSE-23 EE as my project uses new APIs in Java 23 despite the fact that the project will be compiled to Java 22(or older).
What am I missing here?

[iloveeclipse]

What am I missing here?

It is not about running but about compilation level. After this wizard is done, we allow & set Java 23 in compiler preferences for the project but generate and support only Java 22. So user assumes he can use Java 23 JLS but he can't actually.

[akurtakov]

None of them seems to allow setting 23

[iloveeclipse]

None of them seems to allow setting 23

But the actual compiler options file has 23!

[akurtakov]

Now I understand the issue.

[howlger]

The Java compiler setting Use compliance from execution environment 'JavaSE-23' on the 'Java Build Path' does not do what it says, or at least what a user would expect. From the user's point of view the differences between JavaSE-22 and JavaSE-23 are not shown in the Package/Project Explorer, nor in the Java compiler setting (a user will not look at greyed-out/disabled fields).

[akurtakov]

@iloveeclipse What do you think of the approach taken in akurtakov@7a2ac1b ? If this looks fine as idea I'll finish it.
Btw, is there any public API to achieve the same as CompilerOptions.getLatestVersion() ?

[iloveeclipse]

What do you think of the approach taken in akurtakov@7a2ac1b ? If this looks fine as idea I'll finish it. Btw, is there any public API to achieve the same as CompilerOptions.getLatestVersion() ?

See my ideas / comments on eclipse-jdt/eclipse.jdt.core#2606

[akurtakov]

I don't see this directly benefiting the use case here (EE version that the compiler doesn't know about yet) but I will wait for the API changes to shape up before looking further into this one to reduce cross-fire.

[iloveeclipse]

I don't see this directly benefiting the use case here (EE version that the compiler doesn't know about yet)

Exact this use case could be avoided with new API, so Java 23 EE would not appear as allowed EE because there is no compiler support for that.

but I will wait for the API changes to shape up before looking further into this one to reduce cross-fire.

See changes on

• Add new API for supported/unsupported Java versions eclipse.jdt.core#2606
• Drop support for older Java versions in debugger eclipse.jdt.debug#452
• Drop support for older Java versions #1469

For this ticket, the only additional change would be to restrict JavaCore.SUPPORTED_VERSIONS to exclude versions past CompilerOptions.getLatestVersion().

[howlger]

Closed: in the Eclipse SDK 4.33RC2, in the New Java Project dialog, in the Use an execution environment JRE drop-down menu, JavaSE-23 is no longer offered as an option.