We too have debated on this in our previous blogs ( Blog1, Blog2 ).īut, in the process of going with the flow, a lot of developers and engineers alike are sometimes grappling in the dark when it comes to the basic need or necessity for this migration. Some are keen on it and some find it laborious and unnecessary. That means we won’t test or certify our products with OpenJDK and if you have problems and want to open an SR with MOS, you’ll need to test your scenario with Oracle Java first.There is a lot of buzz around users switching to OpenJDK from OracleJDK. It should probably work, especially now as that is now directly based off the Oracle commercial distribution and pretty much includes everything. You can already use Java 11 for Oracle REST Data Services and SQLcl. We have it working internally, and should be good to go soon. The good news is that very soon this year we’ll have official Java 11 support going. Yes, I know it’s 2019 and SQL Developer still requires Java 8. You get to use the Oracle JDK for our products. They’re also all Oracle products that are included with Oracle Database. Oracle SQL Developer, Oracle SQL Developer Data Modeler, Oracle SQLcl, and Oracle REST Data Services are all Oracle products. The TL/DR version of those links basically comes down to this – Oracle products requiring Java, get to use the Oracle JDK at no additional cost. The details behind this can be found in these resources: What does this mean for Oracle SQL Developer users? Your existing licenses gives you access to the Oracle JDK at no additional cost. New terms for using the Oracle JDK went into affect recently, and we’ve seen JDK 11/12 updates released.

The wonderful world of Java has seen some pretty big changes in both licensing and technology lately.

Oracle open jdk