Hello,
I agree too, we should move to at least 17.
versions 12 to 16 have only minor improvements.
With 17 at least we would have an LTS and useful new features : text
blocks, records, switch, sealed classes.
I would even jump to 22 to have Panama if it was just me.
In the past I would agree that updating a JVM could be a trouble, but today,
with all the security concerns and tools like Docker, updating is much
easier and becomes a real need.
If you check Oracle JDK download page :
https://www.oracle.com/java/technologies/downloads/
You can't get version 17 / 11 / 8 without login in.
So maybe 21 should be the new lowest limit.
Johann
Le 15/10/2026 à 08:40, Alexis Manin a écrit :
Hi,
I agree with an update.
However, I would be in favor of increasing the version to at least an LTS
version.
Therefore, I would skip the java 12 update to directly aim for JDK 17.
Maven 4 will require java 17 [1], so if the aim is to migrate the build
system to Maven 4, it will be required soon anyway.
Other major projects in Java ecosystem already require Java 17 : Apache
Tomcat 11 [2], Spring framework (since previous major version) [3],
To note, free update support for JDK 17 has already ended last month [4],
so it would be good to aim for an even higher LTS version short after SIS
1.8 release.
Regards,
[1] https://maven.apache.org/guides/mini/guide-migration-to-mvn4.html
[2] https://tomcat.apache.org/whichversion.html
[3]
https://github.com/spring-projects/spring-framework/wiki/Spring-Framework-Versions#jdk-version-range
[4]
https://www.oracle.com/java/technologies/java-se-support-roadmap.html#javase
Le mer. 14 oct. 2026, 22:07, Martin Desruisseaux via dev <[email protected]>
a écrit :
Hello all
For the next release of SIS, should we increase the minimal Java version
required by the endorsed modules? The current version is Java 11. We
could target Java 17 or 21. If agreed, I propose to start with only Java
12 for SIS 1.8 and move to the high version afterward. The reason for
one conservative step is because some users wanted strongly a low
minimal version in the past, and they may not be following this mailing
list. Doing one step at Java 12 will give us a chance to see if it
causes some reaction after the next SIS release before more substantial
changes.
Note: this proposal has no impact on the "incubator" group of modules,
which is already on a higher Java version.
Martin
