Can't get Groovy working on 8.x Follow
Ok, so I _had_ it working, I thought, under 8.0 M1 (not positive of version, but know I had something properly _executing_ my groovy scripts, though not highlighting properly).
I've installed groovy-1.5.7 on my system.
I've created a new project, added groovy facet and added global lib of Groovy using the embeddable groovy-all JAR file.
No highlighting, no recognizing of runnable scripts, nothing, even when adding files through menu such as "New->Groovy Script".
I've googled and searched these forums, release notes, etc and I'm not new to IDEA (using since 5.0).
What am I missing?
Attached are screens of my settings, except plugins as I only had ONE non-default plugin (older one for highlighting Groovy syntax, but which I disabled and nothing changes.
Tried on:
8.0.1
8.1
Diana build 9618
Help?
Attachment(s):
groovy-lib.png
groovy-facet.png
groovy-no-inspection.png
Please sign in to leave a comment.
Hello, Colin.
Judging by screenshots you've attached, you have wrong file type, associated with *.groovy files (namely, text files, not "Groovy files"). That's why all analyses don't work on them. To fix this, go to Settings -> IDE settings -> File types. Remove *.groovy from "text files" section and add it to "Groovy scripts and classes".
With best regrads,
Ilya
Ah, I would have thought setting Groovy facet and all that up would have fixed or prompted in such a case. Must be that an old setting before I had any groovy support caused that.
Works fine in 8.0.1, but in Diana-9618 I get this (just an FYI, I don't need the EAP release at the moment):
null
java.lang.NullPointerException
at org.jetbrains.plugins.groovy.runner.GroovyScriptRunConfiguration.getConfPath(GroovyScriptRunConfiguration.java:182)
at org.jetbrains.plugins.groovy.runner.GroovyScriptRunConfiguration.configureJavaParams(GroovyScriptRunConfiguration.java:158)
at org.jetbrains.plugins.groovy.runner.GroovyScriptRunConfiguration.access$000(GroovyScriptRunConfiguration.java:62)
at org.jetbrains.plugins.groovy.runner.GroovyScriptRunConfiguration$1.createJavaParameters(GroovyScriptRunConfiguration.java:272)
at com.intellij.execution.configurations.JavaCommandLineState.getJavaParameters(JavaCommandLineState.java:35)
at com.intellij.execution.impl.DefaultJavaProgramRunner.doExecute(DefaultJavaProgramRunner.java:2)
at com.intellij.execution.runners.GenericProgramRunner$1.run(GenericProgramRunner.java:79)
at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.run(LaterInvocator.java:16)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
at com.intellij.ide.IdeEventQueue.c(IdeEventQueue.java:35)
at com.intellij.ide.IdeEventQueue.b(IdeEventQueue.java:99)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:217)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:176)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
Yes, it's known bug. It will be fixed in next EAP.
With best regrads,
Ilya
Fixed. Wait the next EAP