Explore how modules interact with JavaFX

[nipafx]

Some related links:

• https://andresalmiray.com/building-a-layered-modular-java-application-watch-out-for-these/
• exception swallowed by JavaFX classes?
  • https://twitter.com/lanthale/status/1405776799724806144
• Include dependencies in jar javafxports/openjdk-jfx#236 (comment)
• resources, e.g. FXML, CSS

[nlisker]

Some additions:

There is a JavaFX Plugin that configures the JavaFX dependencies without the need to manually specify dependencies and configuration. However, it's not working properly with modules, apparently since it still thinks gradle doesn't know how to handle modules:

• JavaFX plugin forces Gradle to put libraries on the modulepath instead of the classpath openjfx/javafx-gradle-plugin#94
• JavaFX plugin forces Gradle to put libraries on the modulepath instead of the classpath for whitebox unit tests openjfx/javafx-gradle-plugin#133

You need to specify the dependencies manually. If you use the FXML module, because it uses reflection, you also need to open it.

Another point is that JavaFX modules are platform-specific and use a classifier. For example

"org.openjfx:javafx-graphics:$javafxVersion:win"

will download the graphics module for windows. To create a cross-platform application, you need to specify the other platform dependencies too.