Just spreading some more rumors:)

ctrl-B on class and local definition references works, completion works in the same places.Find usages for groovy classes should also work. Ctrl-B from java to groovy classes is also implemented. Formatter is implemented. Grails application development is a work in progress too.

Eugene.

Hmm,

SVN had uncompilable code checked in as of EOD Friday, May 4th (come on, guys..) Reverted couple revisions back, followed the instructions.

With the plugin installed in b6913 can't create any groovy file (groovyfile template something cannot be found error). Noticed the build had some absolute paths hardcoded, could it be the problem? (though why is it hardcoded then?).

Noticed the actual groovy templates (in the plugin jars) are case sensitive, while the error refers to the template in lowercase.

Well, so far the plugin was useless, but you didn't guarantee anything after all

Eugene, hate to report this myself, but after deploying the same plugin version into IDEA once again, the behaviour changed. I don't see Groovy class/script in the New menu anymore, only Grails (?!). Not helpful, I know.

The good news is existing Groovy files are opening fine, reformatting works, highlighting seems to be fine.

Now, if you'd get imports suggested automatically by IDEA, that'd be 50% of the deal of me already personally

I'll keep an eye on the plugin and will report on the issues (hey, do we have JIRA project for it yet?).

It behaves quite differently from other part of IDEA. First, there was no camel humps suggestions for class names.

However, if I fully type the class name (existing, in the library jar), it is highlighted in red, and Alt-Enter suggests the import (nice :). Though it never does it automatically, as for Java classes.

There are other minor issues I came across, which are better put in JIRA or separate threads.

Hello every one, can some one share a build version of this plug in?

thanks