Java license (Java SE Subscription) vs. Free (Open JDK)

Basically, there are now the licensed Java "Enduser" versions (JRE -> Java SE Subscription) and the free development versions (JDK -> http://openjdk.java.net/projects/jdk). Both have the same functions "from end-user" view. In the licensed JRE versions, there are some money security updates (hotfixes) for the major versions (Long Term Support - LTS), in the JDK versions, there is not this update, but you have in quick succession (about every 6 months) always switch to the latest Java version.

TRUECHART vs. Java System requirements

The TRUECHART installer does not contain java anymore from version 2018.2.0. In this sense, Java is always a system requirement for the TRUECHART service. Java is only needed on the server system where the TRUECHART Service is installed. Client systems does not need a Java installation.

So in general customers have to take care of the Java installation and updates (licensing).

What does the new java release cycle mean for my company?

With regard to the Oracle JDK, companies have three possible approaches to choose from and have to weigh them up.

Change to a new Java version every 6 months. If this succeeds, one always builds on the current and free supported version. At the same time, the latest function and security updates are always available to the project.
Purchase of commercial support from Oracle. Then users always migrate from LTS version to LTS version, whereby however in each case large version jumps are necessary. For example, the change from Java 8 to Java 11 is scheduled for the beginning of 2019, and then 2022 from Java 11 to Java 17.
The migration will continue at the pace of the company's own project or according to company guidelines. Commercial support is completely eliminated or can be compensated for the migration to the new version, which is actually necessary, by externally purchased services.

It is perfectly permissible to use a Java version without updates and bug fixes from Oracle - this saves money. However, all published bug fixes and security updates must then be dispensed with. However, bug fixes are only critical if the project is actually affected by this bug. However, every project benefits from the elimination of security vulnerabilities. Therefore, this approach is not without risk and should be carefully considered.

Further links and explanations

EN: Further information can be found here: https://www.oracle.com/technetwork/java/javaseproducts/overview/javasesubscriptionfaq-4891443.html
EN: For a description of the Java licensing topic, there is this 335-page PDF that ends with everything: https://www.oracle.com/technetwork/java/javase/documentation/java-se-lium-2018-03-19 -4421425.pdf.
DE: Generally, this Heise article describes the topic very exhausting: https://www.heise.de/developer/artikel/Wird-Java-jetzt-kostenpflichtig-4144533.html?seite=all.

Browser not supported