Projects fail to load with Gradle 2.3-rc-1 #178
Comments
Thanks for the report. I can reproduce the issue myself. Though, I have no idea the source of the problem yet. |
Here is the stacktrace shown in Netbeans when using gradle 2.3: Issue 1Requested project: Stack trace: |
Looking more at this issue, I believe that this is a bug in Gradle and reported it on the Gradle forums. |
|
Voted! thanks for looking into this and getting the issue raised. |
The issue seems to be fixed in Gradle 2.4-20150218230021+0000. Sadly, this means that Gradle 2.3 will never work with NetBeans (since the bug is in Gradle). |
Just for the reference, if someone really wants to use Gradle 2.3 with NetBeans: Setting "Build script evaluation strategy" to "Idea plugin based" will work but in this case lots of custom settings in the build script will not be recognised. |
Adjusted the plugin to automatically revert to using the old strategy when trying to use Gradle 2.3 (with an appropriate warning). |
From netbeans 8.0.1 I did {note we had to move back to gradle 2.3 since 2.4 didn't work with Team City build :) } |
@kelemen THANK YOU for that tip. Was having problems with Gradle 2.11 and Netbeans 7.3.1 and that fixed it. |
@ray-print What was your problem exactly? I can load projects using Gradle 2.11 without any problem. |
If I remember, first I got the "Cannot determine classpath" error, then the "could not run build action" error. The former was solved by setting some configuration option correctly, the latter by setting "Build script evaluation strategy" to "Idea plugin based" as you suggested. I had a set of problems with Gradle, most of which were probably caused because I don't really understand it yet, and because my computer is old (so I'm stuck at Java 1.6 and old versions of Gradle/Netbeans/Eclipse). |
If you can reproduce the problem, can you open a separate issue with the stack trace of the error included? |
Can't easily reproduce it. On 2/22/16, Attila Kelemen notifications@github.com wrote:
|
What do you know, it is reproducible now. Filed as: #265 |
Seems to have trouble finding the tooling APIs.
The text was updated successfully, but these errors were encountered: