Move to the maxium officially supported version of Java in the docker image

Hi everyone,

I would like to propose to move to the maximum supported version of Java in our docker image, instead of the minimum one (for example currently this means keeping Java 21 for 16.10.x and move to Java 25 for the other branches).

More recent versions generally have various improvements and since they are officially supported there is no reason to stick to the minimum supported version. The maximum supported version also happen to be the most tested version in our CI. We could also imagine an extension that would require a more recent Java version than the minimum supported version of XWiki, right now it could not be used with the docker image.

I would also like to take this into account in release time automation (which is currently in charge of keeping in sync jdbc drivers and libreoffice) based on the information we already have in our pom (the property xwiki.java.version.support). Of course the version would be switched only if there is indeed a tomcat image which does exist for that version of Java (tomcat images are often lagging a bit behind so we usually cannot switch right away when a new LTS is declared supported).

WDYT ?

+1, thank you!

+1 Thx

One issue I see with this would be if we have a maximum supported version that is not a java LTS version (while the minimum one is). Users in production would probably prefer the java LTS version.

This use case does not exist. We only ever indicate LTS major versions in our pom files.

+1 thanks

+1

Thanks,
Marius

5 +1, you can find the PR for that proposal on XDOCKER-432: Use the maximum officially supported version of Java in the Docker image by tmortagne · Pull Request #114 · xwiki/xwiki-docker · GitHub