The current FX build produces a bundle for inclusion in a JDK build. The subsequent build tasks for building apps, building tests, and running tests assume that the bootJDK already has javafx.* modules, and use scripts to patch these existing modules at compile time or runtime.
We can currently build the FX modules using a JDK without javafx.* modules (the "gradle sdk" step), but we cannot build or run apps or tests on such a JDK. We instead have to take those FX bits and build our own JDK including them.
This is a significant limitation, as it effectively requires FX developers to build their own OpenJDK + FX if they want to run an FX app with an OpenJDK build.
We need to enhance the build system to produce artifacts that can run on a boot JDK without javafx.* modules baked in.
NOTE: untill all of the internal dependencies are resolved (see
- blocks
-
JDK-8202368 Create jmods for standalone javafx modules
- Resolved
- is blocked by
-
JDK-8200277 Compiling native media code fails when using OpenJDK build as boot JDK
- Resolved
-
JDK-8199071 Fix gradle deprecation warnings
- Resolved
-
JDK-8202036 Update OpenJFX license files to match OpenJDK
- Resolved
-
JDK-8195788 Remove obsolete javafx.jmx module
- Resolved
- relates to
-
JDK-8202446 Update the scripts in rt/tools/scripts/ for standalone SDK
- Open
-
JDK-8202277 WebView image capture fails with standalone FX due to dependency on javafx.swing
- Resolved
-
JDK-8203378 JDK build fails to compile javafx.graphics module-info.java if FX was built with OpenJDK
- Resolved
-
JDK-8210617 Standalone javafx modules no longer have permissions by default
- Closed
-
JDK-8202451 Swing interop fails when run with a security manager with standalone SDK
- Closed
-
JDK-8195798 ☂ Address dependencies in javafx.* modules on internal APIs of core modules
- Resolved
- links to