Back when Forge switched to use ForgeGradle, I was able to discover a Gradle support plugin- allowing me to load ForgeGradle itself as a NetBeans project, and allowing me to put ForgeGradle's complicated functionality under said IDE's control and therefore easy for me to integrate into my favorite development environment. I used the debugClient to debug my game during that time then, when it said it would be deprecated soon, I tried the instructions- using the runClient command with the --debug-jvm argument. However, that has never worked.
I just updated my development to the just about the latest Forge (1.8-220.127.116.112), and the debugClient task no longer exists, as kinda expected. However, the --debug-jvm argument is also not recognized. I've tried using Gradle versions 2.3 (minimum by ForgeGradle), 2.4 (recommended by NetBeans), and 2.9 (latest), but the same error each time. Even so, I'm still very interested in using my NetBeans debugger- there's a particularly vile bug in my mod that I have to track down through massive numbers of debug statements, instead of pausing the run to take a peek at local variable values & execution results, as the debugger does. Is there a task/argument I can use to get ForgeGradle to incite the JVM's debugger the way the debugClient task did, such that NetBeans can latch into it?