codenarcMain appears to hang when I try to build Gradle

(Justin Stout) #1

This morning I cloned Gradle from github and, following the instructions in the README, ran:

./gradlew idea -i

Right now it says:

…  :buildSrc:codenarcMain  Executing task ‘:codenarcMain’ due to:

No history is available. Loaded properties file in 197ms; 305 rules Loading ruleset from [file:/home/jrs/Documents/Code/gradle/config/codenarc.xml] Loading ruleset from [rulesets/braces.xml] Loading ruleset from [rulesets/imports.xml] Loading ruleset from [rulesets/naming.xml] RuleSet configuration properties file [] not found. Analysis time=6818ms > Loading > :buildSrc:codenarcMain

It has been on this task for almost 12 hours. I don’t have the fastest machine in the world, but I get the feeling it shouldn’t take this long. Did I overlook an important configuration step or something? How do I solve this problem?

Running Fedora 19 64 bit with JDK

(Peter Niederwieser) #2

Hard to say, I haven’t heard of this before. Which OS? Try once more, and if it hangs again, take a thread dump and post it as a GitHub Gist.

(Justin Stout) #3

I’m using 64 bit Fedora Linux 19.

Here’s the thread dump

(Peter Niederwieser) #4

What I don’t understand is that I don’t see any traces of Codenarc in the thread dump.

(Mat Booth) #5


I am seeing the same hang on 64bit Fedora 19.

I am trying to build Gradle 1.6, so I have run the following commands:

$ git clone $ cd gradle/ $ git checkout REL_1.6 $ git checkout -b mbooth $ ./gradlew eclipse

The process has hung after printing the following output to the terminal:


:buildSrc:compileJava UP-TO-DATE







:buildSrc:compileTestJava UP-TO-DATE




:buildSrc:checkstyleTest UP-TO-DATE

Loading > :buildSrc:codenarcMain

If I grep the output of ps for ‘gradle’ there appears to be two Gradle processes running:


org.gradle.wrapper.GradleWrapperMain eclipse

Here are thread dumps of both of those processes:

I can also supply heap dumps, if that would help.

(Peter Niederwieser) #6

I’ve created GRADLE-2858 for this.

(Justin Stout) #7

Switching from OpenJDK to the Oracle JDK solved this problem for me.