I'm not an expert, but there are 3 kind of things that englobe the word "Java".

• Java SE

• Java EE

• Java VM (Runtime and JDK)

SE and EE are just the API (free as in freedom)

About the VM, there are mainly two options (OpenJDK[free] and OracleJDK[non-free])

So, if we write code for SE, or EE we "should" be agnostic about the actual implementation of the APIs (Java VM)

As an example: Running code writen for SE 11 in a OpenJDK runtime is free, but not if it is done with OracleJDK

Java LTS versions are commercial? (meaning not public)

Which means unless your willing to pay for LTS is not available to you. Is that something we should plan on?

I think the concern here about JDK versions is about when public updates are no longer available and plan that a major Sakai version should use a version of Java until the next major Sakai release which would pick up a new version of Java (probably the most current at that time or close to it) so that it will have the best chance of having Java support during that Sakai's release.

https://youtu.be/YauqubC8FKM

Yeah, thats the point, have the 9 and 10 ready in order to face JDK11 as fast as posible.

The hard transition is from 8 -> 9 so after having support for 9, 10 and 11 will be easy

I changed the title, if you don't plan to have this working in JDK 11 on this jira (since it's not yet released) please open a new one for 11.

You're right, that's the one I was thinking of, Sakai 13 should work is JDK 11 LTS (which should be relased in 18.9) before the next release of Sakai. I'm less concerned if it works with 9 and 10 but it would probably need to work in those to work in 11.

http://www.oracle.com/technetwork/java/javase/eol-135779.html