Groovy Grapes support?

Seems Intellij 11 had pretty good groovy support but lacked some things like complete Grapes annotation integration.  I was suprised to see same errors in Intellij 12 and 13 EAP.  Seems this would be high on the list in order to complete groovy support or am I missing something?  What are the benefits of upgrading to 12 or 13 if I'm not doing Android development?  Has there been any real work in maturing groovy and scala support since 11.x?  I see the versions keep increasing for groovy and scala plugins but have not noticed any obvious real world benefits with my projects besides some bugs getting fixed and some new ones being added.  The play 2.x/scala support was not complete either... i would rather see good execution of a few important plugins rather than a large collection of poorly implemented and supported plugins like so many in java community in other projects.

3 comments

What exactly do you lack with regards to Grapes support?

0

Sorry but I already uninstalled the trial Intellij versions 12 and 13.  I hope this is not too vague but my impression was that scripting support is in general worse than Eclipse which is half baked as well.  So all one would have to do is create a Groovy "scripting" project in Intellij (I don't even think Intellij has that concept) and import some dependencies with Grapes and notice that those dependencies are not updated in the project aware classpath and dependencies.  I would expect it to work like Intellij with pom.xml dependencies... you add a dependency and Intellij is aware of it, downloads it and puts it in the classpath so code completion works and there are no compile errors.   Sorry if I overlooked something simple because it seems like this should have been the next logical step for Intellij and Groovy support years ago.

0

Paul, thanks for the reply!
You're right, these dependencies (unlike pom.xml) are not downloaded automatically for the reason that it's harder to manage them (scattered in scripts across project) than the ones from a single pom.xml. There's a request for that: http://youtrack.jetbrains.com/issue/IDEA-56974
Nevertheless there exists a way to get those jars semi-automatically. One should place the caret on the annotation, press the lightbulb (or Alt+Enter) and invoke "Grab artifacts".

0

Please sign in to leave a comment.