Question

My Java stack traces have a lot of entries that I don’t care about, showing method invocation going through proxies and Spring reflection methods and stuff like that. It can make it pretty hard to pick out the part of the stack trace that’s actually from my code. Ruby on Rails includes a “stack trace cleaner” where you can specify a list of stack trace patterns to omit from printed stack traces – what’s the best way to do something like that, universally, for Java?

It’d be best if this worked everywhere, including in the Eclipse jUnit runner.

Answer 1

eclipse has a preference Stack trace filter patterns (look at java > junit or search for stacktrace in the preferences). You can ignore packages (also with wildcards), classes or methods. Does work for direct Test calls (via Run as junit Test), not for commandline runs like ant or maven.