Martin Skurla and I have a basic Gradle plugin working in NetBeans IDE:
As you can see, ".gradle" files are recognized, are shown in the Projects window within a dedicated folder node, and are parsed to show Gradle tasks as children of the file node.
Then, when "Run Gradle" action is invoked on a Gradle task node, which also happens when the Gradle task node is double-clicked, the related Gradle task is run, with output in the Output window.
There's integration with the Groovy Editor, so that's how the syntax coloring and other editor features, such as mark occurrences, shown above, is provided.
We spent most of the time figuring out the regex expression for the node display name and on weird java.lang.ProcessBuilder syntax; the rest of the plugin is pretty standard NetBeans API code.
Not only supported in NetBeans modules, as you can see:
Now, does anyone know what a Gradle task for building a NetBeans module looks like? And for a standard Java SE application and for a web application? I.e., we need to map all the Ant tasks (build, run, debug) to Gradle tasks, if we're not mistaken in our understanding of Gradle.
Can anyone help answer this question or advise in any other way? What should the next features be that should be worked on in this context? And who would be interested in contributing code?