kelemen / netbeans-gradle-project Goto Github PK

I use this plugin to open a gradle project from

https://github.com/Netflix/Hystrix/tree/master/hystrix-examples-webapp

the output panel gives me the following errors, why?

Failed to load Gradle project: hystrix-examples-webapp
org.gradle.tooling.GradleConnectionException: Could not fetch model of type 'IdeaProject' using Gradle distribution 'http://services.gradle.org/distributions/gradle-1.1-bin.zip'.
    at org.gradle.tooling.internal.consumer.ResultHandlerAdapter.onFailure(ResultHandlerAdapter.java:55)
    at org.gradle.tooling.internal.consumer.async.DefaultAsyncConnection$3.run(DefaultAsyncConnection.java:81)
    at org.gradle.messaging.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:66)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)
Caused by: org.gradle.api.GradleException: Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at http://gradle.org/docs/current/userguide/gradle_daemon.html
Please read below process output to find out more:
-----------------------
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.

    at org.gradle.launcher.daemon.bootstrap.DaemonGreeter.parseDaemonOutput(DaemonGreeter.java:37)
    at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startProcess(DefaultDaemonStarter.java:108)
    at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startDaemon(DefaultDaemonStarter.java:89)
    at org.gradle.launcher.daemon.client.DefaultDaemonConnector.createConnection(DefaultDaemonConnector.java:101)
    at org.gradle.launcher.daemon.client.DefaultDaemonConnector.connect(DefaultDaemonConnector.java:72)
    at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:115)
    at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:57)
    at org.gradle.tooling.internal.provider.DaemonGradleLauncherActionExecuter.execute(DaemonGradleLauncherActionExecuter.java:43)
    at org.gradle.tooling.internal.provider.DaemonGradleLauncherActionExecuter.execute(DaemonGradleLauncherActionExecuter.java:30)
    at org.gradle.tooling.internal.provider.LoggingBridgingGradleLauncherActionExecuter.execute(LoggingBridgingGradleLauncherActionExecuter.java:53)
    at org.gradle.tooling.internal.provider.LoggingBridgingGradleLauncherActionExecuter.execute(LoggingBridgingGradleLauncherActionExecuter.java:30)
    at org.gradle.tooling.internal.provider.DefaultConnection.run(DefaultConnection.java:114)
    at org.gradle.tooling.internal.provider.DefaultConnection.getTheModel(DefaultConnection.java:108)
    at org.gradle.tooling.internal.consumer.connection.AdaptedConnection.getModel(AdaptedConnection.java:53)
    at org.gradle.tooling.internal.consumer.ModelProvider.provide(ModelProvider.java:57)
    at org.gradle.tooling.internal.consumer.connection.LazyConnection$2.run(LazyConnection.java:111)
    at org.gradle.tooling.internal.consumer.connection.LazyConnection.withConnection(LazyConnection.java:119)
    at org.gradle.tooling.internal.consumer.connection.LazyConnection.getModel(LazyConnection.java:108)
    at org.gradle.tooling.internal.consumer.connection.ProgressLoggingConnection$2.run(ProgressLoggingConnection.java:67)
    at org.gradle.tooling.internal.consumer.connection.ProgressLoggingConnection.run(ProgressLoggingConnection.java:81)
    at org.gradle.tooling.internal.consumer.connection.ProgressLoggingConnection.getModel(ProgressLoggingConnection.java:65)
    at org.gradle.tooling.internal.consumer.connection.LoggingInitializerConnection.getModel(LoggingInitializerConnection.java:53)
    at org.gradle.tooling.internal.consumer.async.DefaultAsyncConnection$2.run(DefaultAsyncConnection.java:61)
    at org.gradle.tooling.internal.consumer.async.DefaultAsyncConnection$3.run(DefaultAsyncConnection.java:79)
    ... 4 more

See: https://netbeans.org/bugzilla/show_bug.cgi?id=228494

I've created a "Single Gradle project" and it has a "Dependencies" folder, but I can't seem to find a way to add dependencies to it. I expected something like an add option in a "Dependencies" folder context menu, but there's no context menu appearing at all.

Am I overlooking something, is something going wrong or is it simply not possible to add dependencies though the GUI?

Using NetBeans 7.3 on Ubuntu 13.04 (x64).

When i right click on the project in project explored i dont see option to delete the gradle project!

Enable version control when right click in node project.
In a Gradle project, now when I have to confirm changes I have to go to the console outside NetBeans.

Thanks.
Martín.

It looks like JUnit tests are being run (I see output in the build/test-results and build/reports/tests directories), but the output isn't integrated into NetBeans' "Test Results" window. Having to go outside of the IDE to see what tests passed/failed messes with the integrated workflow that IDE ought to provide.

Ideally, these results would be available from within NetBeans, similarly to how the Maven integration works.

Thanks again for a great product, and I'm happy to provide a minimal test case if necessary.

Usability enhancement request.

When navigating in the 'Projects' view using the keyboard arrows we can select projects under a 'Subprojects' node. For now we need to do a right click to open the subprojects. Being able to open selected projects by double-clicking or simply hitting 'Enter' would be nice and provide consistent behavior with native and maven based projects in Netbeans.

I'm using plugin version 1.1.5.1 in a multi-module project.

Steps to reproduce:

1. Right-click on a subproject name in a Projects window and select Build from the context menu.
2. A new tab containing the build output appears in the Output window. Exactly as expected so far.
3. Repeat step 1.
4. The new build output is appended to the output of the previous build. Expected result: the previous output should have been cleared.

Please note that when I select "Tasks -> build" from the context menu, everything works as expected.

Thanks.

Most of my projects show with a yellow triangle and I get this exception:

Failed to load Gradle project: MyProjectNameHere
org.gradle.tooling.BuildException: Could not fetch model of type 'IdeaProject' using Gradle installation 'C:\Tools\gradle'.
at org.gradle.tooling.internal.consumer.ResultHandlerAdapter.onFailure(ResultHandlerAdapter.java:55)
at org.gradle.tooling.internal.consumer.async.DefaultAsyncConnection$2.run(DefaultAsyncConnection.java:71)
at org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:66)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
at org.gradle.tooling.internal.consumer.BlockingResultHandler.getResult(BlockingResultHandler.java:46)
at org.gradle.tooling.internal.consumer.DefaultModelBuilder.get(DefaultModelBuilder.java:46)
at org.netbeans.gradle.project.model.GradleModelLoader.getModelWithProgress(GradleModelLoader.java:234)
...

The projects work fine from the command line. C:\Tools\gradle is the path configured in options->misc->gradle and contains a gradle-1.7 distribution.

In ANT projects, I can associate 3rd parties javadoc to the project in the library manager. I don't see how I could do for Gradle projects. I have a zip file in a local directory and would like to link it to a library.

with ANT :

with Gradle :

Setting anything in Project Properties/License header has no effect and after closing Project Properties and reopening them shows, that the plugin does not save the user entries.

Is there a way to tell netbeans that a project should be loaded as a gradle project even if it has the former nbproject configuration?

A Gradle project can have a 'buildSrc' directory with build related source code.

See http://www.gradle.org/docs/current/userguide/organizing_build_logic.html#sec:build_sources

Having this directory visible in the 'Projects' tree with correct classpath set would be awesome.

Cheers

If gradle is installed by homebrew package manager (Mac OS X 10.8) then the plugin does not except the folder as valid gradle distribution.
Although the gradle installation works otherwise:
$ gradle -version
...Gradle 1.6
and $ which gradle
/usr/local/bin/gradle

Maybe the difference of the directory structure might be the problem:
The directory structure from brew is:
/usr/local/Cellar/gradle/1.6/bin (with a link to ../libexec/bin/gradle)
/usr/local/Cellar/gradle/1.6/libexec
/usr/local/Cellar/gradle/1.6/libexec/bin (with the actual binary)

The directory structure from unzipped downloaded "gradle-1.6-all.zip" is:
gradle-1.6/bin (with the actual binary)
gradle-1.6/lib

What makes a gradle folder a "valid gradle distribution"? What assumptions makes the plugin?

Hello.
Please, make window, in which user will add dependencies, like as in Maven project, with search in Global maven repo and in local Maven repo.

I have written in #58 , but I have question:
You wrote: "It is not possible to add dependencies through the GUI.". Why not possible? In Maven project has window to add deps, for example sreen with window http://s15.postimg.org/beuvl3l3v/image.png . Why you can't use this window? And please - please, just do not close my ticket, because maybe the same discussion. Or you do not want to discuss the possible functional your plugin?

Sorry my bad English.
Best regards, Arthur Khusnutdinov.

I have a multimodule project, in which subprojects apply the java plugin, but the root project doesn't.

When I try to build the root project, it fails with the following output:

Executing: gradle ::build

FAILURE: Could not determine which tasks to execute.

• What went wrong:
  Task 'build' not found in root project 'Ecwid-gradle'.
• Try:
  Run gradle tasks to get a list of available tasks.

BUILD FAILED

I realize that this happens because the 'build' task is not defined in the root project.
However, if I run command 'gradle build' from the command line prompt, it works as expected (builds every subproject).

Could you possibly consider the following change to address this issue:

1. When the 'Build' command is called from the root project, run command 'gradle build' instead of 'gradle ::build'
2. When the 'Build' command is called from a subproject (say, 'mysubproject'), run command 'gradle -p mysubproject build' instead of 'gradle :mysubproject:build'. This item is not necessary, I just suggest it for consistency.

See pictures below. Any idea why that happens?

Standard Java Project with full set of categories:

(Nested) Gradle Project with limited set of categories only:

I find this plugin very good but I can't get hot deployment to work while debugging.

Is this possible?

I can't get Netbeans Gradle plugin to load correctly the Qi4j SDK build.
See https://github.com/qi4j/qi4j-sdk

This project is a Gradle build with many submodules that have valid circular dependencies.

For example:

• core/testsupport depends on core/runtime in compile scope
• core/runtime depends on core/testsupport in test scope

Dependencies are not loaded correctly in Netbeans and I get various behavior when I try to "Reload projects" individually. The plugin seems to not be throwing any exceptions so I have no trace to paste here.

Could you have a look?

Thanks for your time.

/Paul

In contrast to Maven project in Netbeans where you can in Project Explorer open a list of dependencies and select "Download Sources" and "Download JavaDoc", It's not possible to do with current Gradle support plugin.

When working with an open-source framework such as Spring Framework it's often very helpful to dig into the source-code. If NB detects sources in the same directory - then it works. However an automatic download would be very helpful (just like for Maven)

In netbeans/ant, I can write a test case, and press shift-f6 to run it, enabling fast test development.

In netbeans/gradle, shift-f6 doesn't work for junit classes. However, from the associated class, I can ctrl-f6 to 'run the test for this class'.

Please make shift-f6 intelligently work out how to run the class currently being edited, as the default netbeans/ant integration does.

This is currently the only blocker for adopting netbeans/gradle in our organization. The inability to kill a run is an inconvenience, but not a blocker. Otherwise, we love it. Thank you.

Hi,

I am having issues installing the plugin in Netbeans 7.3 Product Version: NetBeans IDE 7.3 (Build 201306052037), Updates: NetBeans IDE is updated to version NetBeans 7.3 Patch 2.

I am getting an error that the groovy plugin cannot be obtained.

Here is the stacktrace:
INFO [org.netbeans.modules.autoupdate.services.InstallSupportImpl]: http://dlc.sun.com.edgesuite.net/netbeans/updates/7.3.1/uc/final/distribution/patch2/groovy/org-netbeans-modules-groovy-gsp.nbm
java.io.FileNotFoundException: http://dlc.sun.com.edgesuite.net/netbeans/updates/7.3.1/uc/final/distribution/patch2/groovy/org-netbeans-modules-groovy-gsp.nbm
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1434)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
at org.netbeans.modules.autoupdate.updateprovider.NetworkAccess$Task$2.call(NetworkAccess.java:161)
Caused: java.io.FileNotFoundException: http://dlc.sun.com.edgesuite.net/netbeans/updates/7.3.1/uc/final/distribution/patch2/groovy/org-netbeans-modules-groovy-gsp.nbm
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1491)
at java.security.AccessController.doPrivileged(Native Method)
at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1485)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1139)
at org.netbeans.modules.autoupdate.updateprovider.NetworkAccess$Task$2.call(NetworkAccess.java:174)
[catch] at org.netbeans.modules.autoupdate.updateprovider.NetworkAccess$Task$2.call(NetworkAccess.java:145)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
INFO [org.netbeans.modules.autoupdate.services.InstallSupportImpl]: Cannot access http://updates.netbeans.org/netbeans/updates/7.3.1/uc/final/distribution/patch2/groovy/org-netbeans-modules-groovy-gsp.nbm
java.io.IOException: Cannot access http://updates.netbeans.org/netbeans/updates/7.3.1/uc/final/distribution/patch2/groovy/org-netbeans-modules-groovy-gsp.nbm
at org.netbeans.modules.autoupdate.services.InstallSupportImpl.copy(InstallSupportImpl.java:987)
[catch] at org.netbeans.modules.autoupdate.services.InstallSupportImpl.doDownload(InstallSupportImpl.java:748)
at org.netbeans.modules.autoupdate.services.InstallSupportImpl.doDownload(InstallSupportImpl.java:679)
at org.netbeans.modules.autoupdate.services.InstallSupportImpl.access$700(InstallSupportImpl.java:91)
at org.netbeans.modules.autoupdate.services.InstallSupportImpl$1.call(InstallSupportImpl.java:193)
at org.netbeans.modules.autoupdate.services.InstallSupportImpl$1.call(InstallSupportImpl.java:134)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
INFO [org.netbeans.modules.autoupdate.ui.wizards.InstallStep]: http://updates.netbeans.org/netbeans/updates/7.3.1/uc/final/distribution/patch2/groovy/org-netbeans-modules-groovy-gsp.nbm
org.netbeans.api.autoupdate.OperationException[PROXY]: http://updates.netbeans.org/netbeans/updates/7.3.1/uc/final/distribution/patch2/groovy/org-netbeans-modules-groovy-gsp.nbm
at org.netbeans.modules.autoupdate.services.InstallSupportImpl.doDownload(InstallSupportImpl.java:821)
at org.netbeans.modules.autoupdate.services.InstallSupportImpl.doDownload(InstallSupportImpl.java:679)
at org.netbeans.modules.autoupdate.services.InstallSupportImpl.access$700(InstallSupportImpl.java:91)
at org.netbeans.modules.autoupdate.services.InstallSupportImpl$1.call(InstallSupportImpl.java:193)
at org.netbeans.modules.autoupdate.services.InstallSupportImpl$1.call(InstallSupportImpl.java:134)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[catch] at java.lang.Thread.run(Thread.java:662)

Kind regards
Thorsten Klaus

For gradle 'war' projects it would be really cool to have some elements from standard NB web projects:

• The Web Pages folder which is linked to the webAppDir configured in the project (usually src/main/webapp)
• The Run category in the NB project properties to be able to deploy directly to a configured server
• The Configuration Files and Server Resources folders, however they are of minor importance

The first day I started playing with the plugin, I created a test project.
After some experiments I closed the project and forgot about it.

Now, while working on a real project, I am constantly notified about errors in that closed test project.
The errors themselves are correct, but I expect IDE would not try to load the closed projects. It is likely to cause performance issues, if the closed project is large or if there is a number of them.
I tried to clear the cache in netbeans userdir folder, but that didn't help.

The exception I unexpectedly get is as follows:

Failed to load Gradle project: Ecwid-gradle
org.gradle.tooling.BuildException: Could not fetch model of type 'IdeaProject' using Gradle installation '/usr/share/gradle'.
at org.gradle.tooling.internal.consumer.ResultHandlerAdapter.onFailure(ResultHandlerAdapter.java:53)
at org.gradle.tooling.internal.consumer.async.DefaultAsyncConnection$3.run(DefaultAsyncConnection.java:81)
at org.gradle.messaging.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:66)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
Caused by: org.gradle.api.internal.LocationAwareException: Build file '/Users/basil/Ecwid-gradle/gradle-run-tasks/build.gradle' line: 31
A problem occurred evaluating project ':gradle-run-tasks'.
at org.gradle.initialization.DefaultExceptionAnalyser.transform(DefaultExceptionAnalyser.java:85)
at org.gradle.initialization.MultipleBuildFailuresExceptionAnalyser.transform(MultipleBuildFailuresExceptionAnalyser.java:47)
at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:115)
at org.gradle.initialization.DefaultGradleLauncher.getBuildAnalysis(DefaultGradleLauncher.java:92)
at org.gradle.tooling.internal.provider.BuildModelAction.run(BuildModelAction.java:70)
at org.gradle.tooling.internal.provider.DelegatingBuildModelAction.run(DelegatingBuildModelAction.java:44)
at org.gradle.tooling.internal.provider.ConfiguringBuildAction.run(ConfiguringBuildAction.java:95)
at org.gradle.launcher.exec.InProcessGradleLauncherActionExecuter.execute(InProcessGradleLauncherActionExecuter.java:39)
at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:45)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:34)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:42)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:24)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.StartStopIfBuildAndStop.execute(StartStopIfBuildAndStop.java:33)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.ReturnResult.execute(ReturnResult.java:34)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:70)
at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:68)
at org.gradle.util.Swapper.swap(Swapper.java:38)
at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:68)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:60)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:34)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:59)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:34)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:45)
at org.gradle.launcher.daemon.server.DaemonStateCoordinator.runCommand(DaemonStateCoordinator.java:186)
at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy.doBuild(StartBuildOrRespondWithBusy.java:49)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:34)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.HandleStop.execute(HandleStop.java:36)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.CatchAndForwardDaemonFailure.execute(CatchAndForwardDaemonFailure.java:32)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.DefaultDaemonCommandExecuter.executeCommand(DefaultDaemonCommandExecuter.java:48)
at org.gradle.launcher.daemon.server.DefaultIncomingConnectionHandler$ConnectionWorker.handleCommand(DefaultIncomingConnectionHandler.java:155)
at org.gradle.launcher.daemon.server.DefaultIncomingConnectionHandler$ConnectionWorker.receiveAndHandleCommand(DefaultIncomingConnectionHandler.java:128)
at org.gradle.launcher.daemon.server.DefaultIncomingConnectionHandler$ConnectionWorker.run(DefaultIncomingConnectionHandler.java:116)
at org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:66)
... 3 more
Caused by: org.gradle.api.GradleScriptException: A problem occurred evaluating project ':gradle-run-tasks'.
at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:54)
at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:127)
at org.gradle.configuration.BuildScriptProcessor.evaluate(BuildScriptProcessor.java:38)
at org.gradle.configuration.LifecycleProjectEvaluator.evaluate(LifecycleProjectEvaluator.java:43)
at org.gradle.api.internal.project.AbstractProject.evaluate(AbstractProject.java:463)
at org.gradle.api.internal.project.AbstractProject.evaluate(AbstractProject.java:75)
at org.gradle.configuration.ProjectEvaluationConfigurer.execute(ProjectEvaluationConfigurer.java:23)
at org.gradle.configuration.ProjectEvaluationConfigurer.execute(ProjectEvaluationConfigurer.java:21)
at org.gradle.api.internal.Actions$CompositeAction.execute(Actions.java:67)
at org.gradle.api.internal.Actions$TransformingActionAdapter.execute(Actions.java:96)
at org.gradle.api.internal.project.AbstractProject.configure(AbstractProject.java:439)
at org.gradle.api.internal.project.AbstractProject.allprojects(AbstractProject.java:434)
at org.gradle.configuration.DefaultBuildConfigurer.configure(DefaultBuildConfigurer.java:32)
at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:142)
at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:113)
at org.gradle.initialization.DefaultGradleLauncher.getBuildAnalysis(DefaultGradleLauncher.java:92)
at org.gradle.tooling.internal.provider.BuildModelAction.run(BuildModelAction.java:70)
at org.gradle.tooling.internal.provider.DelegatingBuildModelAction.run(DelegatingBuildModelAction.java:44)
at org.gradle.tooling.internal.provider.ConfiguringBuildAction.run(ConfiguringBuildAction.java:95)
at org.gradle.launcher.exec.InProcessGradleLauncherActionExecuter.execute(InProcessGradleLauncherActionExecuter.java:39)
at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:45)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:34)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:42)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:24)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.StartStopIfBuildAndStop.execute(StartStopIfBuildAndStop.java:33)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.ReturnResult.execute(ReturnResult.java:34)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:70)
at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:68)
at org.gradle.util.Swapper.swap(Swapper.java:38)
at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:68)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:60)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:34)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:59)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:34)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:45)
at org.gradle.launcher.daemon.server.DaemonStateCoordinator.runCommand(DaemonStateCoordinator.java:186)
at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy.doBuild(StartBuildOrRespondWithBusy.java:49)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:34)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.HandleStop.execute(HandleStop.java:36)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.CatchAndForwardDaemonFailure.execute(CatchAndForwardDaemonFailure.java:32)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecution.proceed(DaemonCommandExecution.java:126)
at org.gradle.launcher.daemon.server.exec.DefaultDaemonCommandExecuter.executeCommand(DefaultDaemonCommandExecuter.java:48)
at org.gradle.launcher.daemon.server.DefaultIncomingConnectionHandler$ConnectionWorker.handleCommand(DefaultIncomingConnectionHandler.java:155)
at org.gradle.launcher.daemon.server.DefaultIncomingConnectionHandler$ConnectionWorker.receiveAndHandleCommand(DefaultIncomingConnectionHandler.java:128)
at org.gradle.launcher.daemon.server.DefaultIncomingConnectionHandler$ConnectionWorker.run(DefaultIncomingConnectionHandler.java:116)
at org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:66)
Caused by: org.gradle.api.tasks.TaskInstantiationException: Could not create task of type 'NodeExec'.
at org.gradle.api.internal.project.taskfactory.TaskFactory$1.call(TaskFactory.java:115)
at org.gradle.api.internal.project.taskfactory.TaskFactory$1.call(TaskFactory.java:110)
at org.gradle.api.internal.AbstractTask.injectIntoNewInstance(AbstractTask.java:126)
at org.gradle.api.internal.project.taskfactory.TaskFactory.createTaskObject(TaskFactory.java:110)
at org.gradle.api.internal.project.taskfactory.TaskFactory.createTask(TaskFactory.java:70)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory.createTask(AnnotationProcessingTaskFactory.java:93)
at org.gradle.api.internal.project.taskfactory.DependencyAutoWireTaskFactory.createTask(DependencyAutoWireTaskFactory.java:39)
at org.gradle.api.internal.tasks.DefaultTaskContainer.add(DefaultTaskContainer.java:50)
at org.gradle.api.internal.project.AbstractProject.task(AbstractProject.java:916)
at org.gradle.api.internal.BeanDynamicObject$MetaClassAdapter.invokeMethod(BeanDynamicObject.java:216)
at org.gradle.api.internal.BeanDynamicObject.invokeMethod(BeanDynamicObject.java:122)
at org.gradle.api.internal.CompositeDynamicObject.invokeMethod(CompositeDynamicObject.java:147)
at org.gradle.groovy.scripts.BasicScript.methodMissing(BasicScript.java:83)
at build_2hcnggaahfk5o8cl8cipp2ddug.run(/Users/basil/Ecwid-gradle/gradle-run-tasks/build.gradle:56)
at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:52)
... 55 more
Caused by: groovy.lang.MissingPropertyException: Could not find property 'ecwid.db.user' on project ':gradle-run-tasks'.
at org.gradle.api.internal.AbstractDynamicObject.propertyMissingException(AbstractDynamicObject.java:43)
at org.gradle.api.internal.AbstractDynamicObject.getProperty(AbstractDynamicObject.java:35)
at org.gradle.api.internal.CompositeDynamicObject.getProperty(CompositeDynamicObject.java:94)
at org.gradle.api.internal.project.DefaultProject_Decorated.getProperty(Unknown Source)
at JettyExec.copyProperty(/Users/basil/Ecwid-gradle/gradle-run-tasks/build.gradle:31)
at JettyExec.(/Users/basil/Ecwid-gradle/gradle-run-tasks/build.gradle:15)
at NodeExec.(/Users/basil/Ecwid-gradle/gradle-run-tasks/build.gradle)
at NodeExec_Decorated.(Unknown Source)
at org.gradle.api.internal.DependencyInjectingInstantiator.newInstance(DependencyInjectingInstantiator.java:62)
at org.gradle.api.internal.ClassGeneratorBackedInstantiator.newInstance(ClassGeneratorBackedInstantiator.java:36)
at org.gradle.api.internal.project.taskfactory.TaskFactory$1.call(TaskFactory.java:113)
... 69 more

It's a minor non-blocker cosmetic issue.

For example, when one source file has errors the project's icon should advertise that the project has errors with a red exclamation mark badge.

Using rootProject.name to override the root project name doesn't recognize by the plugin same with the subprojects when trying to use aliases. By default it uses the directory name.

Examples:

File: settings.gradle
rootProject.name = "NewProjectName" // e.g folder name: Ugly-Legacy-Project // settings for subproject include "NewNameForLegacyModule" project("NewNameForLegacyModule").projectDir = file("UglyNameOfLegacyModule")

Current Output:

Project Name = "Ugly-Legacy-Project"
Subproject Name = "UglyNameOfLegacyModule"

Expected Output:

Project Name = "NewProjectName"
Subproject Name = "NewNameForLegacyModule"

prerequisite: any current NetBeans IDE Dev Version e.g. (Build 201305212300)
and no (valid) gradle path in "Gradle Installation Directory"
and Netbeans Gradle Plugin Version: 1.2.2

Trying to load a gradle project from nightly builds results in:

Failed to load the build script of the project(s). org.gradle.tooling.BuildException: Could not fetch model of type IdeaProjece using Cradle distribution 'http://services.gradle.orgjdistributionsf gradle-1.0-bin.zip'. org.gradle.api.internallocationAwareException: Failed to notify model configuration listener. org.gradle.listenerlistenerNotificationException: Failed to notify model configuration listener. org.gradle.listenerlistenerNotificationException: Failed to notify model configuration listener. jaya.langArraylndexOutOfBoundsException: 7
Failed to load Gradle project: controlsfx
org.gradle.tooling.BuildException: Could not fetch model of type 'IdeaProject' using Gradle distribution 'http://services.gradle.org/distributions/gradle-1.0-bin.zip'.

And there are no task to execute, so I cannot run wrapper task to force gradleVersion.

Doing the same with NetBeans 7.3 (still no gradle path in "Gradle Installation Directory") results in:

Also after loading the project with 7.3 there is a hidden .gradle directory in the project root directory, which does not get created when loading with developer version of NetBeans.

I can`t use pretty NetBeans features: Servlet\EJB generation, JPA mapping, WebServices(not only for client) and others.
It seems Gradle root project is of Java application type(and that functionality is filtered for it in New dialog for example).

I suppose that some of these features based on project structure(add\update descriptors and xml configs) and full Gradle support may take a long time.
Is it possible to enable some of these source generation wizards though with limited functionality ?

When using annotation processors like lombok (http://projectlombok.org/) everything works on the command line, but they are not being executed in netbeans. I've tried this with maven projects, netbeans projects and they work with no problems. I imagine that it's because of how the dependencies are loaded into netbeans.

Do you have any idea what could be happening here? Where can I start looking at to solve this problem?

It appears to be impossible to stop execution of any gradle task from IDE.

Suppose I start the Build command.
Then I try to stop the build by right-clicking the progress bar and selecting 'Cancel process'.
Sometimes the message 'Build failure: gradle build' appears in the console, but nevertheless, the build continues.
The same issue happens for any other task (jettyRun, etc). So I have to kill the jetty from the command line, and that is really not good.

Ideally I'd like to have the Stop and Re-run icons in the output window, unless adding them is really complex.

Using version 1.1.4

Not sure if this is a bug or configuration issue.

When I run a test file I am able to see that the test is executed and run via the Output console tab. However I do not see the visual representation in the Test Results tab.

This is nice to have because on error, the console tab doesn't seem to link to source.
I have tried using the -i to display more information but it wasn't captured by Netbeans.

Project was created via 'gradle adea' and then 'dropped' into Netbeans. Everything loaded without error (source/dependencies/tests).

On a Maven based project you can ask Netbeans to download dependencies sources and javadocs, it would be really nice to get something similar on Gradle based projects.

Hello I'm the guy with the script problem from the gradle issue site http://issues.gradle.org/browse/GRADLE-16

This happens when the project is opened.

Hello.
Please, make window, in which user will add dependencies, like as in Maven project, with search in Global maven repo and in local Maven repo.
Sorry my bad English.
Best regards, Arthur Khusnutdinov.

Netbeans requests that the library project will have jar file built by ant script in order to link it. Otherwise you must use this library as read-only jar and attach its sources.

now it tell me the gradle project isn't a web Project .how can i convert it to a web project or add web support

EDIT (moved description from title to here): The problem is that the Gradle plugin does not allow using some templates.

Sorry to come back with another issue. I have tried to use the Apply Code Change button without success.
I have created a small project with 2 println statements and have executed following steps :

• put a breakpoint between on 1 statement
• modify the text of the second statement
• push "Apply code changes" button => task classes is executed on the project
• push "Continue" button
  => I get everytime the original text on the output.
  Looking at issue #32, it seems that this issue was solved, so I am a bit confused... Am I missing a step or doing something wrong?
  Thanks in advance for your help.

I want to create a new "Gradle Root Project". The new project wizard asks for "Project Name/Location/Folder" and "Maven GroupId/Version".
I want to use a domain name as GroupId e.g. "com.xyz.test".
But as soon as I type the "." I get an error:
"The Maven GroupId is invalid."

I realize that I can add any task I need to the 'Custom Tasks' menu.
However, using it for such frequent tasks as building and running is rather inconvenient.

So I suggest the following changes:

1. Ability to customize the Build command.
   I'd prefer running 'gradle testClasses' instead of 'gradle build' when this command is activated. Simply because testClasses does not create war archives and therefore it is much faster.
   Perhaps, this option can be added to the global gradle settings dialog, or to the project properties dialog.
2. Ability to customize the Run command. Ideally I'd see this featire as follows:
   • The dropdown box in the 'run' toolbar (which now looks disabled) lists all tasks defined in the module.
   • When the 'Run' command is activated, the selected task is executed.

I am willing to implement those features myself. However, before starting I'd like you to share your thoughts of it.
Thanks.

It should be trivial to configure the working directory to use when running your code.

It should be possible to set this as a Gradle project property, much like the mainClass, or in the project property dialog for the built-in tasks.

My gradle root file has some sourcesets like:

sourceSets {
    main {
        compileClasspath += configurations.provided
    }

    integrationTest {
        java.srcDir file('src/integTest/java')
        resources.srcDir file('src/integTest/resources')
        compileClasspath = sourceSets.main.output + configurations.testRuntime
        runtimeClasspath = output + compileClasspath
    }

    soapAccepTest {
        java.srcDir file('src/soapAccepTest/java')
        resources.srcDir file('src/soapAccepTest/resources')
        compileClasspath = sourceSets.main.output + configurations.testRuntime
        runtimeClasspath = output + compileClasspath
    }
}

In my sub projects, my project explorer looks like this:

My sub-project's directory mostly follows Maven like structures, like this:

Can a future plugin revision include the ability to display custom sources sets in the project explorer?

I've recently upgraded to a newer revision of the plugin (716e795), and the custom tasks functionality seems to be broken.
I right-click on the project, select the "Custom tasks" submenu, but do not see any of my custom tasks there. Despite the tasks are defined in .nb-gradle-properties and they used to work.

Also, sometimes the plugin breaks something and Netbeans starts hanging on startup. I have to restore the IDE settings folder from time machine to bring it to life again.
Not sure if those events are related, but it seems to me that the custom tasks editing dialog causes the corruption. At least, for the last time it happened right aftter that.

I have three projects, two are used by the third ( in the screen shot, memoryCache depends or directMemory and timer ). The two libraries are using the gradle maven plugin to install the jar into the local maven repository. The jars show up in the "Compile" dependencies for the memoryCache project. However there are still error markers on lines that import the classes from these libraries and code completion does not work on the classes either.

I see the same behavior in two different installations of Netbeans since I am using 2 different computers to develop this code.

Please see the attached image, it is self explanatory.

This ticket is rather a question than an issue.

I added the gradle wrapper task to my project and set gradleVersion to 1.3-rc-2.
If the "Gradle installation directory" is unset, the tasks are executed by 1.3-rc-2 version of gradle, exactly as I expect. However, if it is set, the gradle installation version is used (namely 1.2).

I don't want to leave the installation directory empty, since it is not recommended in README. However, I prefer tasks always be executed with the version specified in project files.

So my question is: is it possible (with a reasonable effort) to make the plugin honour the gradle wrapper even if the "Gradle installation directory" is set?
Or maybe the issues (mentioned in README) do not take effect (despite the installation directory is unset) if the gradle wrapper is used in the project?

Reported here: http://netbeans.dzone.com/nb-why-i-like-gradle-1

This cannot manifest in a bug because it is not really used concurrently but should be fixed regardless.

When I open the vert-x/mod-mongo-persistor project, the provided dependencies are not loaded nor shown in the Dependencies branch of the project tree.

The project has two provided dependencies:

provided "org.vert-x:vertx-core:$vertxVersion"
provided "org.vert-x:vertx-platform:$vertxVersion"

The vertxVersion is set to 1.2.0-SNAPSHOT which is not in Maven central, but the dependencies don't show up even if you change it to 1.2.3.final. (the latter can be found in Maven central)

Maybe, provided is not a "standard" scope for gradle?

You can check out the project from here:
https://github.com/vert-x/mod-mongo-persistor.git

I have noticed that when I restart Netbeans, the profile is set back to default. That's annoying when Netbeans is restarted several times a day and the profile list is long. For ANT projects we do not have this behaviour. Is it something which could be fixed?

java.lang.IllegalArgumentException: Root cannot be null.
at org.netbeans.modules.java.classpath.SimplePathResourceImplementation.verify(SimplePathResourceImplementation.java:85)
at org.netbeans.modules.java.classpath.SimplePathResourceImplementation.verify(SimplePathResourceImplementation.java:68)
at org.netbeans.modules.java.classpath.SimplePathResourceImplementation.(SimplePathResourceImplementation.java:126)
at org.netbeans.spi.java.classpath.support.ClassPathSupport.createResource(ClassPathSupport.java:77)
at org.netbeans.gradle.project.query.GradleClassPathProvider.getPathResources(GradleClassPathProvider.java:242)
at org.netbeans.gradle.project.query.GradleClassPathProvider.loadPathResources(GradleClassPathProvider.java:352)
at org.netbeans.gradle.project.query.GradleClassPathProvider.findClassPath(GradleClassPathProvider.java:423)
at org.netbeans.modules.java.project.ProjectClassPathProvider.findClassPath(ProjectClassPathProvider.java:73)
at org.netbeans.api.java.classpath.ClassPath.getClassPath(ClassPath.java:628)
at org.netbeans.api.java.source.ClasspathInfo.create(ClasspathInfo.java:290)
at org.netbeans.api.java.source.ClasspathInfo.create(ClasspathInfo.java:310)
at org.netbeans.modules.java.source.parsing.JavacParser.init(JavacParser.java:280)
at org.netbeans.modules.java.source.parsing.JavacParser.parseImpl(JavacParser.java:395)
at org.netbeans.modules.java.source.parsing.JavacParser.parse(JavacParser.java:334)
at org.netbeans.modules.parsing.impl.TaskProcessor.callParse(TaskProcessor.java:595)
at org.netbeans.modules.parsing.impl.SourceCache.getResult(SourceCache.java:225)
[catch] at org.netbeans.modules.parsing.impl.TaskProcessor$CompilationJob.run(TaskProcessor.java:717)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)