OpenJDK 12, 13 and LabKey 19.2

Installation Forum (Inactive)
OpenJDK 12, 13 and LabKey 19.2 Kenny  2019-09-25 07:49
Status: Closed
 

Hi,

I'm trying to run through an install of LabKey 19.2 on RHEL7.

The docs at https://www.labkey.org/Documentation/wiki-page.view?name=supported states LabKey 19.2 requires Java 12, and doesn't support Java 13.

They also have a detailed blog post on this topic at https://www.labkey.com/the-java-shake-up-what-it-means-to-labkey-and-you/

The Install docs at https://www.labkey.org/Documentation/wiki-page.view?name=installComponents state "Install the latest supported release of OpenJDK. " with a link to the Java section at https://www.labkey.org/Documentation/wiki-page.view?name=supported#java. That section talks about LabKey Server requiring OpenJDK 12, which if you follow the link on that page takes you to https://jdk.java.net/12/ which is apparently end of lifed now.

It looks like OpenJDK went from JDK 12 -> JDK 13 this month - on the 17th.

The blog post talks about 19.3 being due in Nov 2019 to track the JDK release cycing introducing support for JDK 13.

With the switch from JDK 12 -> JDK 13 having already happened, should we be installing current production LabKey on OpenJDK 12 since it's the only supported option for the latest LabKey?

I'd really much prefer to use RHEL's supported OpenJDK, but that maxes out at OpenJDK 11 which despite being supported by RedHat is not in the LabKey support matrix.

 
 
Jon (LabKey DevOps) responded:  2019-10-03 11:45
Hi Kenny,

Although the switch happened, it takes time to test. We validate compatibility with JDK versions once 1) they are officially released, 2) our major dependencies support that version, and 3) we run that JDK through our test suites for a reasonable period of time.

Also, there are other components that have to be considered on the development-level. For example, the build system we use (gradle) hasn't released a JDK 13-compatible version. This means we have no means to build or run tests on JDK 13. Looking at a bug that was opened on gradle (https://github.com/gradle/gradle/issues/8681), it was only resolved recently. However, this still requires time to properly test things on our end before we will officially state that we're JDK 13 compatible.

Although JDK 12 is no longer supported by Oracle within the past couple of weeks, things like this is relatively common within software development to where some software manufacturers will make changes and it requires other software developers that are dependent upon other 3rd party developers to try and catch up. For example, after Oracle made changes to Java in Java 9, it took Apache some time to revise Tomcat, Commons-Daemon, and a few other server products to adjust accordingly. Rest assured, we are doing everything we can here to try and keep up!

Regards,

Jon