Decouple from the JDK in 3...2... 11!

JDK 11 update: JavaFX will be decoupled from the JDK

Gabriela Motroc

© Shutterstock / Isil Akdede

Hear ye, hear ye! Starting with JDK 11, JavaFX will be available as a separate module, decoupled from the JDK. This should encourage new contributors to engage in the open source OpenJFX community.

As it turns out, JDK 11 represents more than just the end of the road for Java EE modules — it’s also the end of the road for JavaFX — kind of.

Donald Smith, Sr. Director of Product Management at Oracle announced in a blog post that starting with JDK 11 (due in September this year!), JavaFX will be available as a separate module, decoupled from the JDK.

With the Java Platform Module System in place since Java SE 9, it now makes sense to decouple JavaFX from the JDK, in order to make it available as a separate download.  This will make it easier for developers using JavaFX to have more freedom and flexibility with the framework.  Moreover, with our focus on increasing the release cadence of OpenJDK, JavaFX needs to be able to move forward at a pace driven by the contributions from Oracle and others in the OpenJFX community. Oracle plans to implement this decoupling starting with Java 11 (18.9 LTS).

— Donald Smith

The company also wrote in a white paper that JavaFX new fixes will continue to be supported on Java SE 8 through March 2022 and announced that they are “working with interested third parties to make it easier to build and maintain JavaFX as a separately distributable open-source module.”

SEE ALSO: Taking a closer look at JavaFX

Development of JavaFX started in 2005, but it was officially introduced two years later at JavaOne. The technology was fully open-sourced in 2011 and, in 2012, it became part of the Oracle JDK download.

When one door closes, another opens. Case in point: there is now a GitHub mirror of OpenJFX which can be found here.

If you’re interested in OpenJFX, you can subscribe to the mailing list.

SEE ALSO: 20 JavaFX real-world applications

Waving goodbye to Java Web Start, Java EE & CORBA modules

Speaking of technologies that will not be included in JDK 11, Oracle has decided to extend support for Web Start in Java SE 8 from March 2019, through at least March 2025 but it will not be included in JDK 11 and later.

The explanation can be found in the white paper: “Since it is predominantly a desktop technology, Web Start has some limitations. In particular, it requires a standalone JRE to be installed and maintained on the user’s desktop […] The notion of an application being distributed separately from a standalone JRE is, therefore, quickly fading.”

We’re also waving goodbye to Java EE and CORBA modules, “since standalone versions of the Java EE technologies are readily available from third-party sites, such as Maven Central, there is no need for the Java SE Platform or the JDK to include them.”

Gabriela Motroc
Gabriela Motroc was editor of and JAX Magazine. Before working at Software & Support Media Group, she studied International Communication Management at the Hague University of Applied Sciences.

Inline Feedbacks
View all comments