You are viewing the documentation for Blueriq 14. Documentation for other versions is available in our documentation directory.

The information on this page is subject to change due to the changes in the Blueriq support roadmap as well as the Oracle support roadmap.


The Oracle support roadmap has changed for the Oracle Java SE products1. Starting of September 2017 and updated on September 2021, Oracle moved to a "Long Term Support" (LTS) model for Oracle Java SE products. This means that LTS versions will be targeted for release every two years (was every three years). In addition, feature (major) releases will be targeted for every six months along with quarterly maintenance/security updates. The support roadmap for the Oracle Java SE products will follow the pattern below:

1 https://www.oracle.com/java/technologies/java-se-support-roadmap.html

Impact on Blueriq Java Runtime

Blueriq depends heavily on the JDK for much of its functionality. Since JDK 9 Oracle has a new release scheme (as described above) which also has an impact on the supported Java versions per Blueriq major as described in the paragraph Strategy

Strategy

Our strategy is to compile against LTS versions. This way there is no need to change your environment JDK versions every 6 months. For the non-LTS versions we aim to support them, meaning it is possible to run and create custom code/compile on the non-LTS versions. If possible we will support the next LTS version while compiling on the previous version. This way migrating to a new version of Blueriq only means changing the Blueriq version instead of the need update multiple components within your environment.

Oracle decided to deprecate several modules from the JDK in version 9 and 10 and will remove them in version 11 (e.g. the module java.xml.ws). These modules are necessary to run Blueriq (e.g. java.xml.ws is needed for webservicing purposes). Oracle will deliver these modules via third party dependencies for each matching JDK version starting from JDK 9 and up, compiled against that specific JDK version. It is not possible to add third party dependencies compiled against a higher JDK version then the one Blueriq is using. As a result, from a Blueriq perspective it is not possible to compile against JDK 8 and support JDK 11 at the same time due to the impact of changing the JDK version during the lifetime of a Blueriq major version. The Java support roadmap for the coming Blueriq releases is shown below:

JDK

Blueriq 10Blueriq 11Blueriq 12Blueriq 13Blueriq 14Blueriq 15Blueriq 16Blueriq 17

JDK 8 (LTS)

CompileCompileXXXXXX

JDK 9

Support

Support

XXXXXX

JDK 10

X

Support

XXXXXX

JDK 11 (LTS)

X

X

CompileCompileCompileXXX

JDK 12

X

X

SupportXXXXX
JDK 13XXSupportSupportXXXX
JDK 14XXXSupportXXXX
JDK 15XXXSupportSupportXXX
JDK 16XXXXSupportXXX
JDK 17 (LTS)XXXXIntended supportCompileCompileX
JDK 18XXXXXIntended supportXX
JDK 19XXXXXIntended supportIntended supportX
JDK 20XXXXXXIntended supportX
JDK 21 (LTS)XXXXXXIntended support Compile



  • No labels

5 Comments

  1. Voor alle duidelijkheid ook nog toevoegen dat iedere release 5 jaar support krijgt. Dat maakt het makkelijker om het onderstaande plaatje te lezen.

    1. Dat is niet zo generiek te zeggen Ingrid. Premier support (betaald) is er in ieder geval 5 jaar. Hoe lang er public updates zijn is nog niet bekend gemaakt. Vandaar ook de overlopende kleuren. Extended support (ook betaald) is er zelfs tot 8 jaar.

  2. Dubbel op. Dus ik zou gaan voor "If possible we will support ..."

    1. Je hebt gelijk, bedankt (smile)

  3. Ik zou hier eerst even vertellen wat de minimale gevolgen voor de klant zijn dus b.v. dat ze iedere 3 jaar naar een nieuwe JDK versie moeten upgraden en ieder half jaar naar de laatste versie kunnen upgraden. 

    Daarna zou ik pas in de details duiken.