Issue with _JETGROOVY_EVAL_() in the debugger with grails.
When tyring to evaluate anything in the debugger in a grails app, the result of the evaluation is the following exception.
result = {org.codehaus.groovy.runtime.InvokerInvocationException@15328}Method threw 'org.codehaus.groovy.runtime.InvokerInvocationException' exception.
module = null
node = null
detailMessage = null
cause = {groovy.lang.MissingMethodException@15661}"groovy.lang.MissingMethodException: No signature of method: com.something.AppService._JETGROOVY_EVAL_() is applicable for argument types: () values: []"
stackTrace = {java.lang.StackTraceElement[164]@15330}
Googling only gives me a hit in org.jetbrains.plugins.groovy.debugger.GroovyCodeFragmentFactory!
I dont really have a specific question as I am not really excited to debug grails stuff one more time.
If you have something to say about that, you can say it here.
This is with grails 2.1.3 and intellij 13.0.1
I am pretty sure I saw this error also in intellij 12.
请先登录再写评论。
I'm seeing this issue using IntelliJ IDEA 15.0.5 and Grails 2.5.1. FYI, the variables panel, in the debugger console, contains the values you would expect to see when you try to evaluate something in your app either by hovering over the variable in the editor panel or by bringing up and evaluating a specific expression from your code.
I think a deeper understanding of how IntelliJ IDEA interacts with a JVM when it comes to evaluating an expression would be helpful. The exception I get is, "InvokerInvocationException". It seems like when you evaluate the expression the current app context (stackframe) isn't defined.
Same again .. with Intellij 16 .. I'm sure this used to work with older versions (8 .. i think)
Check if your app is skipping the bootstrap when you start it. I think that was my issue.
Why would it be skipping bootstrap ? Anyway it's not as it's correctly loading some setup from there
The app was configured to skip running the bootstrap when running locally.
Didn't know you could do that !
Disabling the grails-melody plugin helped to resolve this issue for me.
+ 1 for disabling the grails-melody plugin.
Disabling grails-melody worked for me as well.
Disabling grails-melody worked for me too!