Comments on: Grails and Eclipse: Not So Groovy

By: SpringSource: A Groovier Eclipse experience « creatified.com

SpringSource: A Groovier Eclipse experience « creatified.com — Wed, 12 Aug 2009 18:11:29 +0000

[...] Grails applications in Eclipse using the Groovy-Eclipse-Plugin was everything but enjoyable for me. Matthias Käppler summed it up best when he wrote: Grails and Eclipse: Not So [...]

By: David

David — Sun, 19 Jul 2009 13:45:47 +0000

Very useful information, thanks!

By: marcmit

marcmit — Tue, 24 Feb 2009 00:08:30 +0000

Remote debugging seems to work. I have enabled the “Disable Groovy Compiler Generation Class Files” checkbox. Start the app with “grails-debug run-app” instead of “grails run-app”. Then use remote debugging on eclipse by creating a run-config for “External Java Application”, select the correct project and port (normally 5005, check for the text “Listening for transport dt_socket at address: 5005″ in the grails windows) and connect your eclipse to the server.

By: Tramuntanal: Grails

Tramuntanal: Grails — Mon, 19 Jan 2009 08:45:00 +0000

[...] http://brainflush.wordpress.com/2008/05/03/grails-and-eclipse-not-so-groovy/ [...]

By: Barnaby

Barnaby — Mon, 08 Dec 2008 19:58:52 +0000

It worked! … sort of. I was able to import a project and everything worked except the Acegi plugin, which refused to compile. I even imported the jar libraries that were inside of it and it still couldn’t find the classes for things like GrailsUser. Etc.

I feel like it’s sssosooooo close. But alas, I just can’t use Eclipse with Grails. So, back to doing it with Vim, like it’s the 1980’s all over again.

By: Paul at Work

Paul at Work — Sat, 29 Nov 2008 12:41:54 +0000

Regarding the Build Error: “Failed to compile configuration file” … Config.groovy … “No signature of method: groovy.util.ConfigSlurper.parse()”

I was able to fix by adding the JDK tools.jar to the project classpath:
- Project Properties > Java Build Path
- On Libraries tab, click Add External JARs, then select ‘..\jdkx.x.x\lib\tools.jar

This is recommended in the instructions on how to setup the Eclipse IDE pluggin.
See: http://grails.org/Eclipse+IDE+Integration

I am now using Grails 1.0.4.

By: Laura

Laura — Thu, 30 Oct 2008 15:58:53 +0000

Great fix thank you … I have followed it through (2nd try method) and got rid of the original error.

Unfortunately when running grails in Eclipse I now get an error relating presumably to the fact that the /classes directory already exists and was not expected (since i have commented out the delete. I am running OS X Leopard.

Error is
“Compilation error: Directory /Users/laurajtownsend/.grails/1.0.3/projects/testgrails/classes creation was not successful for an unknown reason
: Directory /Users/laurajtownsend/.grails/1.0.3/projects/testgrails/classes creation was not successful for an unknown reason
at org.apache.tools.ant.taskdefs.Mkdir.execute(Mkdir.java:64)….”

Has anyone seen this or can help me fix (comment out?) the part that wants to make the classes directory again?

Thanks

Laura

By: Sachin Mittal

Sachin Mittal — Sat, 04 Oct 2008 08:21:52 +0000

To make a grails project integrate with eclipse on windows is simpler.
set the output location for both java and groovy to:
web-app/WEB-INF/classes
This is mentioned in the post.
change the Clean.groovy to not to delete the classes dir and its contents under web-inf/classes by commenting:
target ( cleanCompiledSources : “Cleans compiled Java and Groovy sources”) {
def webInf = “${basedir}/web-app/WEB-INF”
/*Ant.delete(dir:”${webInf}/classes”)*/
Ant.delete(file:webXmlFile.absolutePath, failonerror:false)
Ant.delete(dir:”${webInf}/lib”)
/*Ant.delete(dir:classesDirPath)*/
Ant.delete(dir:resourcesDirPath)
Ant.delete(dir:testDirPath)
}

note commenting this makes life easier because every time you deploy a war you don’t have to build the project again to repopulate classes dir.

Thanks
Sachin

By: Matthias

Matthias — Mon, 15 Sep 2008 09:04:05 +0000

I only have problems debugging Groovy code after modifying it in a running session. The debugger is then unable to attach the source code to the compilation. I have to restart the servlet container for it to work again.

By: Nestor Urquiza

Nestor Urquiza — Fri, 05 Sep 2008 19:56:36 +0000

It seems like a bug reported as critical on JIRA http://jira.codehaus.org/browse/GROOVY-2208

So the class files are missing LineNumberTable information and that is why Eclipse won’t be able to provide debugging capability for them.

I am wondering if any of you guys found this problem so far? BTW this will affect any IDE and not just Eclipse.