creatified.com » Eclipse

SpringSource: A Groovier Eclipse experience

mat.i.am — Wed, 12 Aug 2009 17:48:10 +0000

For a very long time developing 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 Groovy

In fact I struggled to get the Groovy-Eclipse-Plugin installed those days, and after finally having done that I found out that developing Grails applications in Eclipse was really painful for me.

But now with the first pre-M1 release of the next version of the Groovy-Eclipse plugin many things are better than ever. I finally got around using Grails and Eclipse for some of my projects at work but on the Mac at home I still prefer the combination of TextMate and Console.app. I’m looking forward to the final release which should improve UI performance in Eclipse, especially when using Code Assist.

Eclipse Galileo coming with Cocoa for OS X

mat.i.am — Wed, 24 Jun 2009 13:45:55 +0000

For all the developers using a Mac and Eclipse – be sure to check out the new release of Eclipse “Galileo” which will be out tomorrow, and is now built using Cocoa! Say goodbye to Carbon…

Of course I’ll post my experiences here…

Eclipse and Grails

mat.i.am — Sat, 13 Jun 2009 21:18:27 +0000

In the last weeks I’ve been working on quite some different Grails applications. In my opinion Grails is really a great framework.

But one aspect that’s often annoying me is the Eclipse integration. Like many other guys I’d like to use Eclipse because for me TextMate is no full-blown IDE. But the default integration into Eclipse is “incomplete” at best.

Here are some things I encountered with some possible solutions:

Unfortunately the generated Eclipse project files do not include a source link to the plugins directory of your project. Since Grails 1.1 this will be in your home-directory (at least on Unix-based systems) like ~/.grails/{GRAILS_VERSION}/projects/{PROJECT}/plugins, you will have to link this as a source folder when you’re using any plugins (which will often be the case)

The other thing is: if you’re including jars in the “lib” directory under your Grails project you will either add these jars manually to your build path or once again add this folder as a linked source folder.

I hope these issues will be addressed in a future release of Grails, hopefully as soon as 1.1.2 since these should not be too complicated to fix.