The javafx.* modules use several internal APIs via qualified exports from java.base and java.desktop in the implementation of JavaFX. Additionally, the jdk.packager module uses internal APIs via qualified exports from the jdk.jlink module.
We should enumerate these qualified exports and file linked blocking issues to address them.
- is blocked by
-
JDK-8195799 Use System logger instead of platform logger in javafx modules
-
- Resolved
-
-
JDK-8195800 Eliminate dependency on sun.reflect.misc in javafx modules
-
- Resolved
-
-
JDK-8195801 Replace jdk.internal.misc.Unsafe with sun.misc.Unsafe in MarlinFX
-
- Resolved
-
-
JDK-8195802 Eliminate use of jdk.internal.misc security utilities in javafx.graphics
-
- Resolved
-
-
JDK-8195803 Eliminate use of sun.nio.ch.DirectBuffer in javafx.media
-
- Resolved
-
-
JDK-8195804 Remove unused qualified export of sun.net.www from java.base to javafx.web
-
- Resolved
-
-
JDK-8195806 Eliminate dependency on sun.font.lookup in javafx.graphics
-
- Resolved
-
-
JDK-8195808 Eliminate dependency on sun.print in javafx.graphics
-
- Resolved
-
-
JDK-8198858 Remove use of internal packages of core modules from unit tests
-
- Resolved
-
-
JDK-8195811 Support FX Swing interop using public API
-
- Resolved
-
- relates to
-
JDK-8203378 JDK build fails to compile javafx.graphics module-info.java if FX was built with OpenJDK
-
- Resolved
-
-
JDK-8198329 Support FX build / test using JDK that doesn't include javafx.* modules
-
- Resolved
-
-
JDK-8203379 Remove javapackager sources from OpenJFX repo
-
- Resolved
-
- links to