I've recently upgraded from 1.7.1 to 1.8.0RC1, and have lost stack traces when
running JUnit tests.
These stack traces are missing from both the 'brief' and 'xml' formatters I've
specified. Adding filtertrace="off" causes the stack traces to reappear.
However, that obviously gives me long stack traces.
Because turning off filtertrace partially solves the problem, I'm wondering if
filtertrace is being overly aggressive.
Has anyone else experienced this problem with Release Candidate 1?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]