I would suggest to first set up a simple basic Maven/JavaFX/JDK 9 project outside NetBeans and get that working -- I have a feeling the problem may not be connected to NetBeans but to working with Maven, JavaFX, and JDK 9 together.
Thanks, Gj On Sun, Feb 18, 2018 at 1:09 AM, Chuck Davis <[email protected]> wrote: > Having issues with 205 so updated to 211 this a.m. > > I'm refactoring a project to use jdk9 on the referenced build. It is > a Maven/JavaFX project. > > I've added the module-info class and the project compiles fine. > > The first issue was that the project couldn't find HttpClient (in the > incubator). I appear to have gotten that fixed. > > The next problem is when I try to execute the project it can't find > the main class anymore. As soon as I click the run arrow the main > class selection dialog pops up but is totally unusable -- I think this > is a bug that needs to be fixed before release. ?? > > I've googled and researched a considerable amount. I've added > --main-class to the vm options so that for the release configuration > my vm options look as follows though there appears to be no difference > between "release" and "default" configurations: > > --add-modules=jdk.incubator.httpclient > --main-class=com.yakridge.client.MainApp > > I assume the problem arises somewhere between the classpath and module > path revisions but I don't know that for a fact. I just know I'm > stuck. > > The big question is how do I set the main class for a jdk9/Maven > project? It's specified correctly in the POM. > > Thanks for any guidance. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
