javafx.embed.swt.* regarded as JDK internal API by jdeps of jdk9-ea135

Kevin Rushforth kevin.rushforth at
Tue Sep 13 13:42:40 UTC 2016

That seems surprising since javafx.swt is not part of the JDK runtime 
image. I suspect that this is either an issue with jdeps itself or with 
how you are running jdeps. What was the command line you were using?

As for your second question, the expectation is that javafx.swt will be 
added as an automatic (and thus named) module in a layer, but that still 
needs to be tested. We currently do all of our own testing by adding it 
as an automatic module on the module path as follows:

    $ java --module-path $JAVA_HOME/lib/javafx-swt.jar --add-modules 
javafx.swt my.pkg.MyApp

-- Kevin

Alexander Nyssen wrote:
> Hi all,
> I used a recent jdeps (from jdk9-ea135) to check the Eclipse GEF code base and was astonished to see that all dependencies to javafx.embed.swt.* now seem to be regarded as JDK internal API. I assume this is just a temporal inconsistency. Therefore, let me ask when it is planned to transfer the javafx.swt module into a proper named JIGSAW module to resolve this. The Eclipse community relies on using the javafx.swt module in an OSGi environment (see, and it would certainly be good if conformance tests could be started as early as possible.
> Best Regards,
> Alexander

More information about the openjfx-dev mailing list