JUnit filtertrace patch

[Erik Hatcher <ja...@ehatchersolutions.com>]

Stephane,

Just out of curiousity, why didn't the patch to the "brief" formatter make
it in along with these?

I wanted to give Scott's patch a try and was using the brief formatter to
test it and was still seeing full stack traces, so then looked back and
noticed it had not made it in  your patches.

And yes, the JUnit infrastructure needs a serious overhaul.  Perhaps we
should put that on the 1.9 to-do list also.  The first thing that should be
done when building the next generation of Ant should be to get the testing
infrastructure in place!  :)

    Erik



----- Original Message -----
From: <sb...@apache.org>
To: <ja...@apache.org>
Sent: Sunday, December 09, 2001 8:38 AM
Subject: cvs commit:
jakarta-ant/src/main/org/apache/tools/ant/taskdefs/optional/junit
JUnitTestRunner.java BatchTest.java JUnitTask.java
XMLJUnitResultFormatter.java PlainJUnitResultFormatter.java JUnitTest.java
BaseTest.java


> sbailliez    01/12/09 05:38:19
>
>   Modified:    src/main/org/apache/tools/ant/taskdefs/optional/junit
>                         JUnitTestRunner.java BatchTest.java JUnitTask.java
>                         XMLJUnitResultFormatter.java
>                         PlainJUnitResultFormatter.java JUnitTest.java
>                         BaseTest.java
>   Log:
>   Patch from Scott Stirling <sc...@rcn.com> that allows
>   stack trace filtering for formatters. It will filter out
>   those unneeded frame from Ant and JUnit so the stack will
>   be much more readable.
>
>   nb: Looks like the JUnit task need serious refactoring since we have
>   been adding feature incrementally. It starts to be a real mess,
>   I can barely read my own code :-(



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>