As has been widely covered in the press, Oracle is moving to monetize Java. This document discusses the changes from Oracle that become effective January 1, 2019, and the impact both on OpenEdge developers and users of OpenEdge applications.
Update: the OpenEdge team has certified OpenJDK (from AdoptOpenJDK) for OpenEdge 11.7.4, and is working on a similar certification for OE12.0. The strategy is to continue to certify OpenJDK for all future releases, to give customers a choice of using an open source JDK or a paid-for version that also comes with support from the vendor (Oracle or other vendors who provide this support service).
It is our understanding that all bug fixes and security patches are done with the single OpenJDK code base, which is maintained by a consortium of companies. That version is then used by all vendors to produce the JDK products that they supply to the market, be they open source or paid-for/licensed. When we certify OpenJDK, in this case from AdoptOpenJDK, that implies that all offerings from vendors of that same version are certified and supported.
As a reminder, our Java support policy as described in OpenEdge Platform and Product Availability Guide (community.progress.com/.../1501.openedge-product-availability-guides-and-life-cycle-guide) states that Java patches can be applied to an OpenEdge-certified version of the Java JDK, and it will be fully supported. Customer are, for example, free to apply current patches to Java 8, and in the future Java 11 when that is certified by the OpenEdge team.