This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Gradle is more and more popular, recently Hibernate have moved to gradle to build...it should support gradle in NetBeans... 1.gradle file editor 2.mapping to project action. 3.execute target from context menu. 4.it is better support converting current project configuration(ant, maven) ot gradle config.
No plans to implement such a feature in the standard IDE distribution. Someone may implement a plugin for it, using netbeans.org or some other development site as they prefer.
http://blogs.oracle.com/geertjan/entry/gradle_netbeans discusses this. I do not know anything more than that.
One and a half year has passed since this enhancement has been requested. I reopen this issue, in hope it will now be reconsidered. Gradle has become even more popular and I believe that it will slowly replace Maven and Ant in the future. What I (and I assume many of the users of NetBeans) require in Gradle support is that simply having a build.gradle allows me to open the project in NetBeans and be able to build, run, debug without any further configuration and if the build.gradle changes NetBeans notices it (so that I do not need to reimport, etc.). Currently if I want to use Gradle and NetBeans I need to keep a NetBeans project and gradle project in sync manually (which is troublesome). Also the third party plugin (http://plugins.netbeans.org/plugin/41776/gradle) is broken for me, so I cannot evaluate it.
Thanks for reopening this issues. I hope Netbeans Dream Team can hear the voice from the end user and NetBeans community.
To be a little more constructive, I write down a possible way of the working of a Gradle project in NetBeans. When I choose to open a project NetBeans recognizes that a build.gradle file is in the directory, so allows me to open the "Gradle project" (as with Maven). After opening, NetBeans looks for the dependencies (compile time) of the project (and does this recursively with transitive dependencies). These dependencies are used only for the purpose of analysing the source code while editing it (displaying compile time erros and static analysis). Since Gradle projects may have other Gradle projects as their dependencies, NetBeans should rescan the dependencies whenever a gradle file changes which has been needed when scanning for dependencies. Of course, there can be dependencies in remote repositories and they should be handled the same way as they are handled in a Maven project (SNAPSHOT projects are occasionally redownloaded but others are assumed not to change). Apart from these the user should have way to manually command the IDE to rescan the dependencies if for some reason the NetBeans was unable to detect that it needed a rescan. Of course, there can be many optimizations applied to the above process but for a preliminary implementation, the above mentioned process should be enough.
The NetBeans team has no plans to work on such a feature that I know of. If you would like to, go ahead; Bugzilla is not the place to discuss it.
http://java.net/projects/nb-api-samples/sources/api-samples/show/versions/7.1/misc/GradleSupport
Go to Tools | Plugins in NetBeans and you will find Gradle Support.