Backport JAVA_23 and JAVA_24 JRE constants to 5.10.x

[snicoll]

Please backport for testing Java 23 to 5.10.x as Java 23 is around the corner and the only option AFAICS is to use OTHER.

[marcphilipp]

The plan is to release 5.11 next week. Therefore, no additional 5.10.x release is scheduled.

[snicoll]

@marcphilipp thanks for the reply. While I understand the policy I am wondering what the plan is for projects that have a maintenance policy and need to pick up/build against recent Java versions?

In my case, Spring Boot is in maintenance mode and can't upgrade to JUnit 5.11. However, it will support up to Java 25.

Is there an escape hatch here? Or do we have to create our own condition?

[sbrannen]

While I understand the policy I am wondering what the plan is for projects that have a maintenance policy and need to pick up/build against recent Java versions?

That's a valid question. We discussed it briefly within the team and decided to leave things as-is for the time being.

Is there an escape hatch here?

No, there is currently no escape hatch for JDK versions released after a particular JUnit Jupiter branch is no longer officially supported.

However, I'm going to reopen this issue so that we can discuss the topic again within the team.

[sbrannen]

See also:

• Support arbitrary Java feature versions with JRE conditions #3930
• Support arbitrary Java feature versions with JRE conditions #3931

[marcphilipp]

@snicoll I think the escape hatch would be to document how to use a later version of JUnit with the Spring Boot version that's in maintenance mode, should users want to upgrade. We already have a section for that in our User Guide that Spring Boot's docs could link to. WDYT?

[snicoll]

I've raised this issue for our own needs. And for everyone who has a maintenance policy like ours.

One could argue the current arrangement is quite artificial as all that's needed is a new enum value and everything would work from a JUnit perspective.

[sbrannen]

One could argue the current arrangement is quite artificial as all that's needed is a new enum value and everything would work from a JUnit perspective.

We hope to address that in #3931.

[marcphilipp]

I've raised this issue for our own needs.

@snicoll You mean for your own tests, right? Could you not use a different version of JUnit for the test sources than for the main sources?

[marcphilipp]

Team decision: Backport the enum constants to 5.10.x and 5.11.x.