I fully agree with you the way forward is using named modules. The reason I
ran into this issue was that I wanted to create a regression test: it
should not work if the modules are not on the module-path. And
surprisingly, it did work.
The current check in the Launcher is hiding potential issues.
Hi Johan,
The intention is to launch using --module-path
java --module-path path-to-sdk/javafx-sdk-11/lib ...
For non-modular applications you also need to add the modules to the
module graph, for example:
java --module-path path-to-sdk/javafx-sdk-11/lib --add-modules
Hi,
I'm a bit confused on the different options for launching JavaFX
applications with the latest Java 11 code.
When running an app from maven, it worked fine. Maven uses the classpath
and not the module path, so I assumed that running the same app using
java -cp all-javafx-jars Main
would work
