Open ssy-lehmann opened 5 years ago
Late answer but i had a similar problem, that i could solve by using a Main-class that did not extend Application
, so hat no direct JavaFX-dependencies. This just called App::main()
, which did extend Application. This works for some reason.
Hi,
If you take a look at https://github.com/StegmannSystems/javafx.demo you can see that your mechanism mvnw clean javafx:run works fine. However that's just interesting for the purpose of testing.
See the following problem:
I can solve it like this:
The main point here is that I already fetched all Java FX dependencies via pom.xml and I shouldn't be forced to specify those two parameters (at least not the module path). Do you have any clever trick on how this can be done more comfortable for maven-shade-plugin and launch4j (at least javafx:run seems to know)?