Compile to older JDK (run on Java 21, but generate Java 17 classes)

[chrislake]

I am beginning the process of updating and evaluating whether our RCP products can be updated to use Java 21. However, not all the other tools we (and QA) use support the handling of Java 21 class files. One of our QA tools may well be quite slow in getting to supporting Java 21, but we don't really want that to be a blocker to updating. I thought then that perhaps we can go down the route of running our products on Java 21 (we force the JRE used by our users for our products anyway), but compile for Java 17 classes which our other tools will happily be able to read.

Within Eclipse I can:

• Add and activate Java 21 in the "Installed JREs" list;
• Set the "Compiler compliance level" to Java 17;
  • Check (or not) the "Use '--release' option".
• Keep the .classpath (JRE_CONTAINER) files to require "StandardVMType/JavaSE-17"
• Update the Target (targetJRE) and Manifest.MF (RequiredExecutionEnvironment) files to require "JavaSE-21"

And this works well within Eclipse and exported products running on Java 21.

However, when running Maven with Java 21, the following example code won't compile with Tycho (4.0.6):

// Compiling source files to C:\java\classes using Eclipse Compiler for Java(TM) 3.36.0.v20231114-0937
locale = Locale.of("pt");
// The method of(String) is undefined for the type Locale
threadID = Thread.currentThread().threadId()
// The method threadId() is undefined for the type Thread

I've update the Pom (maven.compiler.* properties) files with various combinations of , and for the compilers. However, I can't seem to find settings for Tycho, or modifications to other files, to compile everything using Java 21 APIs, but create Java 17 classes.

Is this even possible?

I was hoping to get further than just updating the installed JDK and temporarily adding @SuppressWarnings("deprecation") on everything deprecated since Java 17.

[laeubi]

Set the "Compiler compliance level" to Java 17;
Keep the .classpath (JRE_CONTAINER) files to require "StandardVMType/JavaSE-17"
Update the Target (targetJRE) and Manifest.MF (RequiredExecutionEnvironment) files to require "JavaSE-21"

These are two contradictory settings (even though it theoretically works) as you say your bundle requires Java 21 bytecode but you compile to Java 17 ... You can run any BREE 17 bundle on Java 21 so why enforce it if you want be compatible with Java 17?

So at a first sight there is some chance to confuse the tools by giving different configurations, so what benefit do you expect from requiring Java 21 as BREE?

Technically without special configuration, Tycho (4.0.6) is not able to compile Java 21 you need at least use ECJ 3.37 but the error you are seeing here is most likely because the --release flag is used with Java 17 now and then the method is not available. You can specify -X to maven to see the full compiler options (and used JVMs) so you should look there to get an idea what options are actually passed.

However, I can't seem to find settings for Tycho, or modifications to other files, to compile everything using Java 21 APIs, but create Java 17 classes.
Is this even possible?

I must confess that it works in the IDE seems like a bug to me, even though its hard to tell without the exact configuration, but if you really have a .classpath of "StandardVMType/JavaSE-17" (what maps to a real Java 17 VM) or using '--release 17' then this code should not compile in the IDE when you are using 17+ APIs.