First of all, thanks for gradle, it's a fantastic tool with a lot of maven-killing potential. I'm doing my part to spread the word :)
I recently succeeded in getting my gradle environment set up in IntelliJ IDEA using the instructions here as a guide: http://docs.codehaus.org/display/GRADLE/How+to+set+up+the+Gradle+project+in+IntelliJ I found the instructions were a little out of date, though, as the test suite in particular required a little extra poking. I recorded the steps I needed to build and run the test suite. I would update the page myself with the important steps, but I'm not sure about the best solutions to some of the issues. Here's what I found: To get the lib directory for step 9, you must run gradle ide Compile error in org.gradle.build.release.Svn - Solve by running gradle ide in buildSrc, and add svn-kit*.jar , svnkit-javahl*.jar and xmlunit-*.jar to the classpath. Test suite fails on EclipseWtpTest because expectedWtpFile.txt isn't present - Add ?*.txt to resources Test suite fails on DefaultScriptCompilationHandlerTest because ClasspathTester.dat isn't present - Add ?*.dat to resources Test suite fails on MainTest because gradle.home isn't set I added a System.setProperty("gradle.home", "roadToNowhere") in the setUp, and this solved the failure. I suppose you could also change your IDE's run configuration for All Tests to add this VM parameter, but isn't it better to make the test work on its own? Then the -Dgradle.home could then also be removed from the build.gradle script. Test suite fails on ClasspathConverterTest - I had set up groovy 1.5.7 in IDEA, and it seems that the behavior of flatten is different since 1.5.6. Flatten with a null element in the collection under 1.5.7 throws a NullPointer, causing the test to fail. I fixed this by switching to 1.5.6. Any advice, particularly for the MainTest problem? Thanks Neil
