This was using Gradle 6 and it seems after doing some more builds and then configuring Gradle in the options NetBeans is able to load the project...
Odd thing is the IDE did detect the Gradle binary correctly so maybe the repeat build finally produced something on disk? It's a big project so I don't know / have time to produce a small sample that reproduces the problem. I think this would be much easier to track down if the compiler output would be saved somewhere by the Gradle project support. It was failing in there for some reason but can't know what it was. Maybe some -D property to dump this in an output window or in the log? --emi mie., 29 apr. 2020, 18:15 Peter Steele <steeleh...@gmail.com> a scris: > Run the build on the command line to see if it's a netbeans issue, if it > is then run with With --info or --debug (logging levels) or with > --stacktrace to get the stack trace info of the build failure. > > If it works on the command line then you need to setup gradle properly in > netbeans. > > On Wed, 29 Apr 2020, 07:30 Emilian Bold, <emilian.b...@gmail.com> wrote: > >> Hello, >> >> I have a Gradle based project that won't load in any version of >> NetBeans, including the 12 beta. The notification shown says: >> >> > Compilation failed; see the compiler output for details. >> > Execution failed for task: '<some build task>' >> > Execution failed for task: '<some build task>' >> > Could not run build action using Gradle installation '<path to gradle >> wrapper dists/ folder>' >> >> How does one go about investigating this problem? >> >> For starters, I don't see anything in the output window or messages.log. >> >> Where is the compiler output with the details? >> >> A minor issue: the notification itself (being a Swing component) doesn't >> allow you to copy-paste the error message. >> >> --emi >> >