On 2018-10-13T19:46:34 +0200 Johan Vos <johan....@gluonhq.com> wrote:
> The Java launcher (in the Java 11 JDK) checks if your main class extends > Application, and in that case it checks the module path and tries to find > javafx.graphics module. If you have that module on the classpath, but not > as a module, the launcher will exit with the message you see. > > There are some workarounds (e.g. you can have a Main class that doesn't > extend Application that calls your Application), but the best approach is > go modular, as explained here: > https://stackoverflow.com/questions/52467561/intellij-cant-recognize-javafx-11-with-openjdk-11/52470141#52470141 Ah, ok, thanks! I'm an OSGi user and although the vast majority of the library code I write is JPMS modularized, the application code I write almost certainly won't ever be (because I use OSGi rather than the JPMS). I'm fine with not extending Application - in fact I won't even have the option to do so because OSGi applications don't have that traditional main() method. Is there documentation somewhere on the workaround you mentioned? -- Mark Raynsford | http://www.io7m.com
