Java 9 is obsolete in just six weeks (20th March 2018). What? You haven't upgraded yet? Well, Java 10 is only going to last six months before it is obsolete too.
Update 2018-03-20: Java 10 is released. Java 9 is obsolete.
Release train impact
The new Java release train means that there will be a new release of Java every six months. And when the next release comes out, the previous release is obsolete.
What do I mean by obsolete?
In practical terms it means that there are no more security updates from Oracle. (Theoretically, the OpenJDK community could release security updates, but there is no sign of this yet). And since you don't want to run your software without the latest security updates, you are expected to upgrade to Java 10 as soon as it is released.
As a user of Java, here are three possible ways to approach the release train:
- Stay on Java 8, the current LTS (long term support) release, until the next LTS release occurs (Java 11)
- Move from Java 9 to Java 10 to Java 11, making sure you update rapidly to get the security updates
- Stay on Java 9 (or Java 10) and don't worry about security updates
If you have already moved to Java 9, you have effectively committed to option 2 or 3. If you care about security updates, you need to be prepared to switch to Java 10 shortly after it is release on 20th March. To do this, you probably should be testing with a Java 10 pre-release now. If you find that to be a challenge, you have to stop caring about security, or consider going back to Java 8 LTS.
However you look at it, being on the release train is a big commitment.
- Will your dependencies work on the next version?
- Will your IDE be ready?
- Will your build tool (Maven, Gradle etc.) be ready?
- Will your other tools (spotbugs, checkstyle, PMD etc.) be ready?
- How fast are you going to be able to update when the release you are on is obsolete?
Lots to consider. And given the number of external tools/dependencies to consider, I think its fair to say that its a bold choice to use Java 9 or 10.
Summary
With a release every six months, it is important to decide on an approach to the release train. If you want to upgrade every six months, great! But you'll need to test pre-releases of Java with your whole toolchain in advance of the release to ensure you don't get stuck on an unpatched obsolete release of Java.
