Comments on: Groovy stacktrace folding

By: Peter Gromov

Peter Gromov — Tue, 03 Aug 2010 08:00:55 +0000

Laird,

Actually, it sort of does. If you run a script and there’s an exception, all the lines which correspond to *.java code will be removed. I guess the assumption was that the only Java code executed in a Groovy program is Groovy internals, which is often not true.

By: Laird Dornin

Laird Dornin — Tue, 03 Aug 2010 00:09:31 +0000

Why doesnt Groovy just edit its own stack traces?

java.lang.Throwable {
public java.lang.StackTraceElement[] getStackTrace();
public void setStackTrace(java.lang.StackTraceElement[]);
}

By: Juan Hernandez

Juan Hernandez — Wed, 19 May 2010 11:38:39 +0000

Nice feature.

+1 to user configurable via UI

I could include then …
org.jboss.el.util.ReflectionUtil.* (or org.jboss.el.util.ReflectionUtil.invokeMethod)
com.intellij.rt.execution.application.AppMain.main

By: Peter Gromov

Peter Gromov — Fri, 07 May 2010 07:10:17 +0000

To everyone who asked. ConsoleFolding plugin with configuration UI available at http://plugins.intellij.net/plugin/?idea&id=4975

By: Dan Sheehan

Dan Sheehan — Fri, 23 Apr 2010 14:03:42 +0000

+1 to AOP filtering
+1 to user configurable via UI

By: Jim Bethancourt

Jim Bethancourt — Thu, 22 Apr 2010 17:22:35 +0000

+1 for Geoffrey’s suggestion on filtering the AOP/Proxy reflection stacktraces listed by Spring. Great idea!

By: Geoffrey De Smet

Geoffrey De Smet — Thu, 18 Mar 2010 09:20:03 +0000

This could be usefull in spring stacktraces too: to hide all the AOP proxy and reflection stuff under a + sign.

By: Stephan Anft

Stephan Anft — Thu, 18 Mar 2010 08:31:17 +0000

Very nice. I would love to see this feature in “normal” Java code, too. For example a button in the run console that filters out all stack trace lines referring to classes from external libraries.

By: Peter Gromov

Peter Gromov — Thu, 18 Mar 2010 08:00:37 +0000

Hamlet, not exactly. The current not-to-step-into-list doesn’t allow to step into DefaultGroovyMethods while not stepping to everything else in groovy.*. While I’m not so sure whether I need to step into that code, I definitely want to see it in the stack traces.

The idea of combining the two lists is very attractive, although maybe too dare, but the stepping filters are actually a JVM feature and have a very restricted format, which AFAIK doesn’t allow for exclusions like DGM. It also doesn’t support filtering for specific methods in the class, (e.g. in the java.lang.reflect.Method we filter out only the invoke() method). So, it’s not that simple.

By: Hamlet D'Arcy

Hamlet D'Arcy — Thu, 18 Mar 2010 06:41:16 +0000

Peter, the UI for which packages to filter can be the exact same list as which packages to _not_ step into. The settings panel already has this list. I opened a bug for exactly this a few months ago.

Great improvement gang, thanks!