...

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. 

Stategy

This change in support from Oracle needs to be adapted by Blueriq. 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.

Blueriq depends heavily on the JDK for much of its functionality. 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:

^{* The end of the Maintance & Support phase depends on the Maintenance and Support Agreement. Please read our Support roadmap or contact our customer support if you have any questions regarding the Maintenance and Support Agreement.}