Problem with Grails 2.0.2 and IntelliJ IDEA 10.5.4

[Göran Ehrsson]

Grails Team!

Thank you for releasing 2.0.2 today. The change log is a joy to read (as usual).

But Grails 2.0.2 broke my IntelliJ 10.5.4 because the path to groovy-all-1.8.6.jar has changed.

IntelliJ can't find org.codehaus.groovy.tools.RootLoader or any Groovy class.

This is how it changed:

grails-2.0.1/lib/org.codehaus.groovy/groovy-all/jars/groovy-all-1.8.6.jar

grails-2.0.2/lib/org.codehaus.groovy/groovy-all/1.8.6/jar/groovy-all-1.8.6.jar

Manually moving groovy-all-1.8.6.jar to a location that matches Grails 2.0.1 solved the problem.

grails-2.0.2/lib/org.codehaus.groovy/groovy-all/jars/groovy-all-1.8.6.jar

People on IntelliJ IDEA 11.x did you manage to upgrade to Grails 2.0.2 without problem?

(if you did, I might consider an upgrade)

Regards

/Goran Ehrsson

[OverZealous]

Göran Ehrsson wrote:

But Grails 2.0.2 broke my IntelliJ 10.5.4 because the path to groovy-all-1.8.6.jar has changed.

IntelliJ can't find org.codehaus.groovy.tools.RootLoader or any Groovy class.

IntelliJ 10.x is not compatible with Grails 2.0.  I'm surprised it has worked at all.

People on IntelliJ IDEA 11.x did you manage to upgrade to Grails 2.0.2 without problem?

(if you did, I might consider an upgrade)

I'm running the latest IJ 11.  It doesn't give me any trouble.  However, I don't do in-place Grails upgrades.  I keep each version of Grails in its own folder (grails-2.0.1, grails-2.0.2, etc).  When I get a new version of grails, I create a new shared library within IJ pointing to the new release.  (This is easiest done by making a new Grails project from within IJ, then selecting the new Grails when prompted.)  It's a minor hassle, but it also allows you to keep different versions of grails around as needed, and only upgrade individual projects as you choose.

I use a slightly modified version of grails.sh (https://github.com/deluan/grails.sh) to allow me to run grails from the command line with the correct version for the current project.

- Phil

[Göran Ehrsson]

A strange thing is that groovy-all-1.8.6.jar is visible in IntelliJ (Edit Library) but somehow it will not recognize it as the Groovy bundle to use.

This is the error I get inside Intellij when it tries to sync dependencies (I have not even tried to start Grails from within the IDE yet).

Exception in thread "main" java.lang.NoClassDefFoundError: org/codehaus/groovy/tools/RootLoader

Caused by: java.lang.ClassNotFoundException: org.codehaus.groovy.tools.RootLoader

at java.net.URLClassLoader$1.run(URLClassLoader.java:202)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(URLClassLoader.java:190)

at java.lang.ClassLoader.loadClass(ClassLoader.java:306)

at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)

at java.lang.ClassLoader.loadClass(ClassLoader.java:247)

java.lang.NullPointerException

at org.jetbrains.groovy.grails.rt.Agent$2.run(Agent.java:70)

at java.lang.Thread.run(Thread.java:680)

IDEA hook: Grails not found!

But my workaround to move the groovy-all-1.8.6.jar seems to work ok so I'll let this be for now.

/Göran

29 mar 2012 kl. 20:30 skrev Göran Ehrsson:

Grails Team!

Thank you for releasing 2.0.2 today. The change log is a joy to read (as usual).

But Grails 2.0.2 broke my IntelliJ 10.5.4 because the path to groovy-all-1.8.6.jar has changed.

IntelliJ can't find org.codehaus.groovy.tools.RootLoader or any Groovy class.

This is how it changed:

grails-2.0.1/lib/org.codehaus.groovy/groovy-all/jars/groovy-all-1.8.6.jar

grails-2.0.2/lib/org.codehaus.groovy/groovy-all/1.8.6/jar/groovy-all-1.8.6.jar

Manually moving groovy-all-1.8.6.jar to a location that matches Grails 2.0.1 solved the problem.

grails-2.0.2/lib/org.codehaus.groovy/groovy-all/jars/groovy-all-1.8.6.jar

People on IntelliJ IDEA 11.x did you manage to upgrade to Grails 2.0.2 without problem?

(if you did, I might consider an upgrade)

Regards

/Goran Ehrsson

[Göran Ehrsson]

Argh!! Sorry I hit the send button to early.

Moving the groovy-all-1.8.6.jar did not work at all. I breaks starting Grails from the command line. :-(

It works from within the IDE though.

Messy!

How can the exact path to a jar be so important?

/Göran

29 mar 2012 kl. 21:00 skrev Göran Ehrsson:

A strange thing is that groovy-all-1.8.6.jar is visible in IntelliJ (Edit Library) but somehow it will not recognize it as the Groovy bundle to use.

This is the error I get inside Intellij when it tries to sync dependencies (I have not even tried to start Grails from within the IDE yet).

Exception in thread "main" java.lang.NoClassDefFoundError: org/codehaus/groovy/tools/RootLoader

Caused by: java.lang.ClassNotFoundException: org.codehaus.groovy.tools.RootLoader

at java.net.URLClassLoader$1.run(URLClassLoader.java:202)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(URLClassLoader.java:190)

at java.lang.ClassLoader.loadClass(ClassLoader.java:306)

at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)

at java.lang.ClassLoader.loadClass(ClassLoader.java:247)

java.lang.NullPointerException

at org.jetbrains.groovy.grails.rt.Agent$2.run(Agent.java:70)

at java.lang.Thread.run(Thread.java:680)

IDEA hook: Grails not found!

But my workaround to move the groovy-all-1.8.6.jar seems to work ok so I'll let this be for now.

/Göran

29 mar 2012 kl. 20:30 skrev Göran Ehrsson:

Grails Team!

Thank you for releasing 2.0.2 today. The change log is a joy to read (as usual).

But Grails 2.0.2 broke my IntelliJ 10.5.4 because the path to groovy-all-1.8.6.jar has changed.

IntelliJ can't find org.codehaus.groovy.tools.RootLoader or any Groovy class.

This is how it changed:

grails-2.0.1/lib/org.codehaus.groovy/groovy-all/jars/groovy-all-1.8.6.jar

grails-2.0.2/lib/org.codehaus.groovy/groovy-all/1.8.6/jar/groovy-all-1.8.6.jar

Manually moving groovy-all-1.8.6.jar to a location that matches Grails 2.0.1 solved the problem.

grails-2.0.2/lib/org.codehaus.groovy/groovy-all/jars/groovy-all-1.8.6.jar

People on IntelliJ IDEA 11.x did you manage to upgrade to Grails 2.0.2 without problem?

(if you did, I might consider an upgrade)

Regards

/Goran Ehrsson

[Göran Ehrsson]

Ok, so now I got it working from both Intellij and from the command line.

Solution: Two Grails 2.0.2 installations:

1. .../grails-2.0.2            unmodified for all work outside IDEA.

2. .../grails-2.0.2.idea   with groovy-all-1.8.6.jar moved to satisfy IDEA 10.5.4

I was thinking about having one installation with a symlinked jar, but I don't want  to mess with this anymore.

/Göran

29 mar 2012 kl. 21:12 skrev Göran Ehrsson:

Argh!! Sorry I hit the send button to early.

Moving the groovy-all-1.8.6.jar did not work at all. I breaks starting Grails from the command line. :-(

It works from within the IDE though.

Messy!

How can the exact path to a jar be so important?

/Göran

29 mar 2012 kl. 21:00 skrev Göran Ehrsson:

A strange thing is that groovy-all-1.8.6.jar is visible in IntelliJ (Edit Library) but somehow it will not recognize it as the Groovy bundle to use.

This is the error I get inside Intellij when it tries to sync dependencies (I have not even tried to start Grails from within the IDE yet).

Exception in thread "main" java.lang.NoClassDefFoundError: org/codehaus/groovy/tools/RootLoader

Caused by: java.lang.ClassNotFoundException: org.codehaus.groovy.tools.RootLoader

at java.net.URLClassLoader$1.run(URLClassLoader.java:202)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(URLClassLoader.java:190)

at java.lang.ClassLoader.loadClass(ClassLoader.java:306)

at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)

at java.lang.ClassLoader.loadClass(ClassLoader.java:247)

java.lang.NullPointerException

at org.jetbrains.groovy.grails.rt.Agent$2.run(Agent.java:70)

at java.lang.Thread.run(Thread.java:680)

IDEA hook: Grails not found!

But my workaround to move the groovy-all-1.8.6.jar seems to work ok so I'll let this be for now.

/Göran

29 mar 2012 kl. 20:30 skrev Göran Ehrsson:

Grails Team!

Thank you for releasing 2.0.2 today. The change log is a joy to read (as usual).

But Grails 2.0.2 broke my IntelliJ 10.5.4 because the path to groovy-all-1.8.6.jar has changed.

IntelliJ can't find org.codehaus.groovy.tools.RootLoader or any Groovy class.

This is how it changed:

grails-2.0.1/lib/org.codehaus.groovy/groovy-all/jars/groovy-all-1.8.6.jar

grails-2.0.2/lib/org.codehaus.groovy/groovy-all/1.8.6/jar/groovy-all-1.8.6.jar

Manually moving groovy-all-1.8.6.jar to a location that matches Grails 2.0.1 solved the problem.

grails-2.0.2/lib/org.codehaus.groovy/groovy-all/jars/groovy-all-1.8.6.jar

People on IntelliJ IDEA 11.x did you manage to upgrade to Grails 2.0.2 without problem?

(if you did, I might consider an upgrade)

Regards

/Goran Ehrsson

[Göran Ehrsson]

29 mar 2012 kl. 20:55 skrev Phil DeJarnett:

IntelliJ 10.x is not compatible with Grails 2.0.  I'm surprised it has worked at all.

To clarify: I never start Grails from inside IntelliJ, so I don't need the 11.x features that works with Grails 2.x. I only use IntelliJ for it's awesome Grails editing features. It worked perfectly well with 10.5.4 up until today with Grails 2.0.2.

I also keep multiple Grails versions in Intellij without problem. I switch between 1.3.7 and 2.0.1 projects every day.

/Göran

[Paolo DiCanio]

 IntelliJ 10.x is not compatible with Grails 2.0.  I'm surprised it has worked at all.

Grails 2.0.0 and 2.0.1 work fine on IntelliJ 10.5.4, though obviously it doesn't recognise 2.0.X specific features like using methods for actions or new dynamic finders like findOrCreate.

I've opened a ticket about this issue with Jet Brains:
http://youtrack.jetbrains.com/issue/IDEA-83893

[Göran Ehrsson]

I can confirm that Grails 2.0.3 solves the groovy-jar problem with IntelliJ 10.5.4.

Now I can use the standard Grails download again.

Thank you Grails Team for the fast update!

/Göran

2 apr 2012 kl. 11:21 skrev Paolo DiCanio:

IntelliJ 10.x is not compatible with Grails 2.0.  I'm surprised it has

worked at all.

Grails 2.0.0 and 2.0.1 work fine on IntelliJ 10.5.4, though obviously it
doesn't recognise 2.0.X specific features like using methods for actions or
new dynamic finders like findOrCreate.

I've opened a ticket about this issue with Jet Brains:
http://youtrack.jetbrains.com/issue/IDEA-83893


--
View this message in context: http://grails.1312388.n4.nabble.com/Problem-with-Grails-2-0-2-and-IntelliJ-IDEA-10-5-4-tp4516438p4525518.html
Sent from the Grails - user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[olivertynes]

I get this error with a freshly downloaded intellij IDEA + grails 2.1.0,

----------
IDEA hook: Grails not found!
| Error java.lang.reflect.InvocationTargetException
| Error at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| Error at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| Error at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| Error at java.lang.reflect.Method.invoke(Method.java:597)
| Error at org.jetbrains.groovy.grails.rt.Agent$2.run(Agent.java:73)
| Error at java.lang.Thread.run(Thread.java:680)
| Error Caused by: java.lang.NullPointerException
| Error at org.jetbrains.groovy.grails.rt.GrailsSettingsGetter.printSettings(GrailsSettingsGetter.java:62)
| Error ... 6 more
----------------

Any takers?
Is this the same bug?

-Oliver

On Tue, Apr 3, 2012 at 4:50 PM, Göran Ehrsson <[hidden email]> wrote:

> I can confirm that Grails 2.0.3 solves the groovy-jar problem with IntelliJ
> 10.5.4.
> Now I can use the standard Grails download again.
>
> Thank you Grails Team for the fast update!
>
> /Göran
>
> 2 apr 2012 kl. 11:21 skrev Paolo DiCanio:
>
>
>
> IntelliJ 10.x is not compatible with Grails 2.0.  I'm surprised it has
>
> worked at all.
>
>
>
> Grails 2.0.0 and 2.0.1 work fine on IntelliJ 10.5.4, though obviously it
> doesn't recognise 2.0.X specific features like using methods for actions or
> new dynamic finders like findOrCreate.
>
> I've opened a ticket about this issue with Jet Brains:
> http://youtrack.jetbrains.com/issue/IDEA-83893
>
>
> --
> View this message in context:
> http://grails.1312388.n4.nabble.com/Problem-with-Grails-2-0-2-and-IntelliJ-IDEA-10-5-4-tp4516438p4525518.html
> Sent from the Grails - user mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

--
*****
Oliver Tynes
Developer
Uni CIPR -- www.cipr.uni.no
55588266
*****

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[OverZealous]

Please don't reply unrelated and/or old threads — it's better (and less confusing) if you start a new one.  (See the subject for why this is confusing!)

This is a known problem in IntelliJ, see this page for the IntelliJ bug track on this item, plus a temporary solution:  http://youtrack.jetbrains.com/issue/IDEA-86261

- Phil DeJarnett

Oliver Severin Tynes wrote:
> I get this error with a freshly downloaded intellij IDEA + grails 2.1.0,







---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email