8

I'm using IntelliJ Idea 8.1.2 for Grails development. The dynamic nature of Groovy is giving me a hard time debugging my code: I keep ending up in the internals of Groovy/Grails, i.e. CachedMethod, ExpandoMetaClass or the like.

Is there a way for example to tell the Idea debugger to completely skip the Groovy/Grails internals while debugging and only make steps in my own code? I did notice that there is a configuration option named "Do not step into specific Groovy classes" in Debugger > Groovy but so far I've noticed no difference.

If not, what is your workaround or how do you cope with the situation? Any help would be greatly appreciated.

miek
  • 3,446
  • 2
  • 29
  • 31

2 Answers2

11

File->Settings->Debugger->Stepping

Do not step into the classes...

  • I added 'groovy.*' and 'org.codehaus.groovy.*' and by a quick test it seems to work just the way I wanted it to. Thank you so much! – miek Jun 10 '09 at 07:17
  • 1
    My current exclusion patterns are: groovy.*; org.codehaus.groovy.*; org.springframerwork.*; org.mortbay.* (for Jetty) – miek Jun 11 '09 at 05:41
1

Yeah, I suffer with this annoyance, too, and I don't have a good solution. My workaround once I'm lost in Groovy/Grails code is just to figure out where I should be back in my code, set a break point there, and hit Continue.

Ben Williams
  • 2,297
  • 2
  • 19
  • 15