BT

Your opinion matters! Please fill in the InfoQ Survey!

IntelliJ IDEA 7 adds Groovy and Grails Support

| by Geoffrey Wiseman Follow 0 Followers on Dec 05, 2007. Estimated reading time: 1 minute |

A note to our readers: As per your request we have developed a set of features that allow you to reduce the noise, while not losing sight of anything that is important. Get email and web notifications by choosing the topics you are interested in.

Dynamic language support is becoming an increasingly common part of Java IDEs. NetBeans 6 has Ruby integration, Eclipse has the DLTK and Aptana, and IntelliJ IDEA 7 offers support for Ruby as well as support for Groovy and Grails (it made its first appearance in milestone 2 and will coming out of beta shortly). The support includes:

Groovy code editor with advanced coding assistance, smart completion, code quality maintenance with intelligent code inspections, quick-fixes, refactorings and more, all tied together to create an excellent Groovy and Grails development environment.

In addition to code completion and navigation, refactoring, syntax and error highlighting, code formatting, folding, factoring and debugging in Groovy code, IDEA also offers Grails generators, Groovy Server Pages (GSP) support, and even a ER diagram of your Grails model classes.

Reactions have generally been positive. Glen Smith experimented with JetGroovy, and said:

I'm only a week in, but the things I use all the time are the quick switch options between Domain/Controller/View/Test for a given object. That saves so much time... (in screengrab below I have everything related to the Entry domain class instantly onscreen)

screengrab

Bart suggested that the plugin could "singlehandedly get people playing with Grails and Groovy. Looks like a winner."

On the other hand, Shawn Hartsock rates the Groovy plugin, "Not Quite Good Enough":

The plugin is painfully close to being useful without actually getting in my way. When it comes down to it I must be able to declare my domain classes in packages and the JetBrains plugin can't handle that. Importing existing Grails projects is also more than a gigantic pain. If not done just right you lose all the nifty editor decorations that help with navigation. Also, if you alter your domain model to not use the "default" package you lose the navigation decorators and the ability to generate Controllers and Views inside the IDE.

He did say that it's a great first attempt, but that it's wasn't quite where he wanted it to be.

For more information, watch the demo, a presentation by Eugene Vigdorchik, a developer for JetBrains, and the Grails IDEA Integration documentation.

Rate this Article

Adoption Stage
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Discuss

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT