For now at least not the whole overview of the controller to lose domains and views, it is perhaps time, the IDE support for Groovy and Grails to look at. The IDE of my choice is Eclipse. It is open source, and with its diversity, the plugin Swiss army knife of development environments (albeit a rather large 
).
For Groovy and Grails are the following update URL quite a nice plugin with highlighting and a few other amenities.
http://dist.codehaus.org/groovy/distributions/update/
For a pure Groovy project is available in this article on Eclipse Zone .. a pretty good guide with screenshots
The Grails integration with Eclipse, it is of course a section in the excellent documentation of Grails. I have very good experience with the following steps:
- Installation of the Groovy Eclipse plugin, as described above
- Creating your own Workplaces for Grails projects, pointing to the folder where the actual Grails projects are
- Adaptation of Eclipse, as described in the documentation described
- Creating a new Grails project on the command line with
grails create-app - Creating an Eclipse project with the same name of the Grails project. This will be the same with all libraries included in the classpath of Eclipse.
Conclusion: In my favorite IDE Eclipse plugin that Groovy is the best choice to manage Grails projects. Not succeeded so far is the launch of a Grails project from Eclipse. Since the command line but with grails run-app works great and the changes during development are also immediately deployed, it is easy to get over. If someone has a solution for it, I would be very grateful to him anyway.
Update: the latest version of the paper I have to improve maintainability as part of a small tutorial to Grails, and outsourced direct links in the right sidebar.
For now at least not the whole overview of the controller to lose domains and views, it's perhaps time, the IDE support for Groovy and Grails to look at. The IDE of my choice is Eclipse. It is open source, and with its diversity, the plugin Swiss army knife of development environments (albeit a pretty big :-)). For Groovy and Grails are the following update URL quite a nice plugin with highlighting and a few other amenities. There http://dist.codehaus.org/groovy/distributions/update/ For a pure Groovy project in this article on Eclipse Zone .. a pretty good guide with screenshots The Grails integration with Eclipse, there is naturally a section in the excellent documentation of Grails. I have very good experience with the following steps: Install the Groovy Eclipse plugin, as described above, create your own Workplaces for Grails projects, pointing to the folder where in fact the Grails projects are adaptation of Eclipse, as described in the documentation Creating a new Grails project on the command line with grails create-app create an Eclipse project with the same name of the Grails project. This will be the same with all libraries included in the classpath of Eclipse. Conclusion: In my favorite IDE Eclipse plugin that Groovy is the best choice to manage Grails projects. Not succeeded so far is the launch of a Grails project from Eclipse. Since it works on the command line but with grails run-app and the super changes during development are also immediately deployed, it is easy to get over. If someone has a solution for it, I would be very grateful to him anyway. Update: I have the latest version of the paper I for better maintainability as part of a small tutorial to Grails, and outsourced direct links in the right sidebar.
gklinkmann written by \ \ tags: eclipse , grails , ide
June 8th, 2007 at 10:33 am
Hello
nice article to get into the groovy world. Thank you for that. What excites me most is the fact that Java is groovy. As far as I have just tried, I can call my EJB's in a groovy class (not tried the other way around)
Since this blog entry since even now some time has passed, it would be nice to know how your experiences have become.
What about the refactoring? The code completion SharpDevelop reminds me of my beginnings .... and reacts very slowly with me even when I press CTRL + SPACE.
Furthermore, I do not like it I do not object jdoc or call the help for the respective methods and available. For beginners, the Java + Eclipse spoiled but are somewhat bumpy start. If it is written in their own classes is not possible, the jdoc can (with mouseover, etc.) to indicate the language would unfortunately not feasible in our development team. Keyword: factors and constraints
Maybe I also make what is wrong ....
June 10th, 2007 at 10:15 am
I do not think you're doing something wrong. The Eclipse plugin is also in my view, be improved. This is also the fact why it is not used in our development team.
I've used so far only for Grails prototype. In this area there is in my view, but nothing with which one can quickly achieve results with a customer to have a discussion platform. Especially with the Hibernate tools that are available as a plugin for Eclipse available, can quickly develop a Web application for an existing database model.
Soon I would like to establish Grails for Web tests. A blog entry about it will follow.
March 14th, 2011 at 7:01 am
[...] Again to write a blog entry on this subject (may result in more). One of my first article on Grails showed how to make Grails and Eclipse together. This entry was so successful that I [...]