Thanks Hans. The build seems to be working in IDEA now no problem, but strangely when I open up a Java subclass of a Groovy object I get: Class "blah" must either be declared abstract or implement abstract method invokeMethod(String, Object) in groovy.lang.GroovyObject, which appears to be a compile error, yet the IDEA output directory seems to have the class no problem. Not a real issue, but any pointers..?
Thanks Neil On Tue, Feb 24, 2009 at 2:51 PM, Hans Dockter <[email protected]> wrote: > > On Feb 19, 2009, at 6:01 AM, Neil Curzon wrote: > > 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 >> > > Right. This is new and not covered yet but is the recommended way of doing > things. > > 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. >> > > I see this as a bug of the ide task. I think it is worth a Jira. > > 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 >> > > That's the way we solve the problem. Is this not mentioned on the Wiki? To > figure this out might take a while ... > > >> >> 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. >> > > You are right. We should set this in the MainTest setUp. I think this is > the only place were we need it. There might be a historical reason why it is > the way it is now. Could you file a Jira with fix for 0.6? > > 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. >> > > We had this problem with 1.5.7 as well. Therefore we haven't switched. We > plan to directly switch to 1.6 as soon as it is release. > > An update of the pages would be very appreciated. > > - Hans > > -- > Hans Dockter > Gradle Project lead > http://www.gradle.org > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
