Well you are hitting: https://issues.apache.org/jira/browse/NETBEANS-2004
I'm going to update it with your comments.
Unfortunately there is no trivial throw in solution to the problem, at
least not one I know of, that support needs a proper implementation.
I was trying to do something easy to provide classpath as module path to
the IDE, but that did not really worked. Probably need to parse the
Gradle created java command line arguments for that.
On 3/8/19 9:00 AM, Scott Palmer wrote:
I just recently attempted to make a modular project.
I’m using JavaFX so I tried the somewhat-official javafx gradle
plugin and used the modular gradle example from here:
https://github.com/openjfx/samples/tree/master/CommandLine/Modular/Gradle/hellofx
NetBeans is not happy with this at all.
module-info.java claims the javafx.controls module cannot be found
The code editor complains about all the javafx imports stating that:
"package javafx.scene is not visible
(package javafx.scene is declared in the unnamed module, but
module javafx.scene does not read it)"
Does anyone know the solution?
From the command line ‘“gradle build” works without any complaints.
It looks like NetBeans sees the JavaFX stuff as added to the class
path instead of the module path.
I can use JavaFX in a non-modular way, and I can hack the Gradle
manually to insert —add-module and —module-path args to various build
steps, but I was trying to do things based on the examples.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
