I’ve been trying this out since it has Gradle support built in, but I’m seeing a number of problems (master branch). Building with Linux, 11.0.2-open (OpenJDK), Gradle 4.10.2.
These are some of my observations so far:
NetBeans 11 “open” of the root project and all subprojects reports a number of problems out of the box. These could be NB Gradle support bugs, since that’s pretty new.
I’m able to do a successful* build from the command line (*it says it’s successful, I wouldn’t call it success). A “gradle run” gets me to the test demo dialog fine, so that’s good. But the very last thing before “BUILD SUCCESSFUL” is a crash from Javadoc - see #3 below.
When I do a command line build of one of the projects that fails in NetBeans (jme3-vr), I get a crash during Javadoc generation. There’s an open bug filed on Oracle’s old JDK bug site for this exception back as far as JDK 9. Interestingly, when I build with JDK 12 this crash turns into about 100 or so warnings. So I could probably fix that for 11, using those warnings as a guide.
Other subprojects report “problems” in NetBeans, but allegedly build successfully if I click Clean and Build Project. I’ll go into details later if I don’t find a simple cause.
I’m going to continue trying to work through these issues (maybe resulting in some bug reports to NetBeans if that can be determined), but if anyone has any insights or suggestions, I’m listening.
I use sdkman so it’s trivial to switch to virtually any other non-Oracle version of Java or Gradle to try those out (Windows users, you should be jealous). I’ve also tried Java 8, with similar results (at least the vr javadoc crash doesn’t happen), which leads me to believe this is more about the NB Gradle support.