JavaFX Media module crashes jdeps

[Scott Palmer]

Thanks, that does seem to be the issue.

Is this the sort of thing that might be back-ported to a 11.0.2 release?
I'm trying to automate as much of my build as possible and special casing
stuff to work around issues like this makes things a bit messy.  It's just
one of several little things that is making moving beyond JDK 8 a rather
tedious affair.  Almost there though...

Cheers,
Scott


On Mon, Dec 3, 2018 at 12:45 PM Kevin Rushforth <kevin.rushforth at oracle.com>
wrote:

> I should add that fixing the following bug in JavaFX should avoid the
> problem:
>
> https://bugs.openjdk.java.net/browse/JDK-8211900
>
> It's on my list to fix for openjfx12.
>
> -- Kevin
>
>
> On 12/3/2018 9:27 AM, Kevin Rushforth wrote:
> > I guess you are running into:
> >
> > https://bugs.openjdk.java.net/browse/JDK-8211887
> >
> > -- Kevin
> >
> > On 12/3/2018 9:21 AM, Scott Palmer wrote:
> >> I use a Gradle script to run jdeps to get a module list for jlink.
> >>
> >> This command line (excuse the long paths into the Gradle cache):
> >>
> >> jdeps --print-module-deps --module-path
> >>
> C:\Users\spalmer\.gradle\caches\modules-2\files-2.1\org.openjfx\javafx-fxml\11.0.1\2ef70dd2fee84fa4f18c9cbdcabe91e93e8b08ea\javafx-fxml-11.0.1-win.jar;C:\Users\spalmer\.gradle\caches\modules-2\files-2.1\org.openjfx\javafx-web\11.0.1\4912c3f5184d1bea0f8d25af976aab1a521081ac\javafx-web-11.0.1-win.jar;C:\Users\spalmer\.gradle\caches\modules-2\files-2.1\org.openjfx\javafx-controls\11.0.1\c4a7cbfbb28713a29883f7c1c3433b841239f8e7\javafx-controls-11.0.1-win.jar;C:\Users\spalmer\.gradle\caches\modules-2\files-2.1\org.openjfx\javafx-controls\11.0.1\61cf91bf3494d0616216f49c9e1d183d170adf0a\javafx-controls-11.0.1.jar;C:\Users\spalmer\.gradle\caches\modules-2\files-2.1\org.openjfx\javafx-swing\11.0.1\c02350b12b940cb6ed14f1755e056c6e557f8b48\javafx-swing-11.0.1-win.jar;C:\Users\spalmer\.gradle\caches\modules-2\files-2.1\org.openjfx\javafx-media\11.0.1\d261eabc16e8037e403785dcd822b9d42079dc42\javafx-media-11.0.1-win.jar;C:\Users\spalmer\.gradle\caches\modules-2\files-2.1\org.openjfx\javafx-media\11.0.1\fd095047b7d06f6c7b16afe8cf9dffccab5d4494\javafx-media-11.0.1.jar;C:\Users\spalmer\.gradle\caches\modules-2\files-2.1\org.openjfx\javafx-graphics\11.0.1\8ec761df8ab0df38ea43f4e7a3018a2991f786f6\javafx-graphics-11.0.1-win.jar;C:\Users\spalmer\.gradle\caches\modules-2\files-2.1\org.openjfx\javafx-graphics\11.0.1\e062cb01783effc6413abbd94d1838f6b0add209\javafx-graphics-11.0.1.jar;C:\Users\spalmer\.gradle\caches\modules-2\files-2.1\org.openjfx\javafx-base\11.0.1\24f4f0f3a4c3e1ea536e463781fe799e3a7ac857\javafx-base-11.0.1-win.jar;C:\Users\spalmer\.gradle\caches\modules-2\files-2.1\org.openjfx\javafx-base\11.0.1\f1354a284f4151d20358e776f6ff68ee35bbb96d\javafx-base-11.0.1.jar
>
> >> C:\path\to\my\Application.jar
> >>
> >> Causes this exception:
> >> Exception in thread "main" java.lang.NullPointerException
> >>          at
> >>
> jdk.jdeps/com.sun.tools.jdeps.ModuleGraphBuilder.requiresTransitive(ModuleGraphBuilder.java:124)
> >>          at
> >>
> jdk.jdeps/com.sun.tools.jdeps.ModuleGraphBuilder.buildGraph(ModuleGraphBuilder.java:110)
> >>          at
> >>
> jdk.jdeps/com.sun.tools.jdeps.ModuleGraphBuilder.reduced(ModuleGraphBuilder.java:65)
> >>          at
> >>
> jdk.jdeps/com.sun.tools.jdeps.ModuleExportsAnalyzer.modules(ModuleExportsAnalyzer.java:124)
> >>          at
> >>
> jdk.jdeps/com.sun.tools.jdeps.ModuleExportsAnalyzer.run(ModuleExportsAnalyzer.java:97)
> >>          at
> >>
> jdk.jdeps/com.sun.tools.jdeps.JdepsTask$ListModuleDeps.run(JdepsTask.java:1023)
> >>          at
> >> jdk.jdeps/com.sun.tools.jdeps.JdepsTask.run(JdepsTask.java:560)
> >>          at
> >> jdk.jdeps/com.sun.tools.jdeps.JdepsTask.run(JdepsTask.java:519)
> >>          at jdk.jdeps/com.sun.tools.jdeps.Main.main(Main.java:49)
> >>
> >> Without the JavaFX modules listed the output works fine.
> >>
> >> So I started to narrow it down and found that
> >> javafx-media-11.0.1-win.jar seems to cause the exception
> >>
> >> If I make a Java runtime that includes the same JavaFX modules (with
> >> media) and use --system instead of --module-path it also works fine.
> >>
> >> Got any ideas what might be going on?
> >>
> >> Thanks,
> >>
> >> Scott
> >>
> >
> >
>
>
>