Intellij 8.0.1 issues with Grails 1.1 beta2 3

Posted by mjwall on December 29, 2008

Grails-1.1-beta2 does not work correctly with the jetgroovy plugin in intellij. I am able to add a global library for Grails 1.1 beta2, but it not saved in the project facet. The most apparent problem for me is that the ‘Run grails target’ shortcut is not available. See this thread and this bug for more details. According to the details, it is fixed. However, I don’t see an update to the jetgroovy plugin. I am running version 8.0.1 of Intellij on Mac OSX.

So I tried the EAP 9572 version to see if it included the fix that was reported in Jira. The bundled jetgroovy plugin appears to have the update. Yippee. Glad I didn’t have to build it myself according to the wiki,

Here is the interesting part that you may care about. I zipped up the plugins/Groovy folder and replaced the old version in Intellij 8.0.1. It seems to have fixed it for the stable version as well. Here is the file until JetBrains has something better. Use at your own risk, perhaps making a backup of the old plugins/Groovy folder.

UPDATE It appears there are issues with copying the plugin back to the 8.0.1 release. Loading the file inside grails-app just hangs. However, the EAP version is working just fine so far. Let me know if you have success getting it work in the stable version.

UPDATE 2 See this for a patched version that works better.

Trackbacks

Use this link to trackback from your own site.

Comments

Leave a response

  1. Pratik Patel Mon, 29 Dec 2008 23:42:12 EST

    I was going to spend the evening learning how to build Intellij plugins….. thanks to you I can do something more interesting. cheers!

  2. mjwall Mon, 29 Dec 2008 23:54:18 EST

    I’d be interested to know if it works for you.

  3. Pratik Patel Tue, 30 Dec 2008 01:55:17 EST

    Well, I ended up just using the EAP. Couldn’t get 8.0.1 to work with the groovy plugin JAR’s from the 9572 EAP.
    On a side note, it seems like if you make Java 1.6 the default Java on Mac OSX, the EAP bombs on loading some Cocoa-Java JNI stuff. Seems like Apple is not supporting Cocoa-Java moving forward: http://lists.apple.com/archives/java-dev/2008/Apr/msg00286.html

Comments