Documentation patch from Scott Stirling <scottstirling@rcn.com>

about stack filtering.


git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@270101 13f79535-47bb-0310-9956-ffa450edef68

docs/manual/OptionalTasks/junit.html

@@ -60,6 +60,11 @@ elements</a>.</p>
       (errors are considered failures as well).</td> 
     <td align="center" valign="top">No.</td>
 </tr>
+  <tr>
+    <td valign="top">filtertrace</td> 
+    <td valign="top">Filter out junit and ant stack frames from error and failure stack traces.</td> 
+    <td align="center" valign="top">No, default is "on."</td>
+  </tr>
   <tr>
     <td valign="top">timeout</td> 
     <td valign="top">Cancel the individual tests if the don't finish
@@ -220,6 +225,12 @@ can be specified.</p>
       (errors are considered failures as well). Overrides value set in &lt;junit&gt;.</td> 
     <td align="center" valign="top">No.</td>
 </tr>
+  <tr>
+    <td valign="top">filtertrace</td> 
+    <td valign="top">Filter out junit and ant stack frames from error and failure stack 
+    traces.  Overrides value set in &lt;junit&gt;</td> 
+    <td align="center" valign="top">No, default is "on."</td>
+  </tr>
   <tr>
     <td valign="top">todir</td> 
     <td valign="top">Directory to write the reports to.</td>
@@ -295,6 +306,12 @@ generates a test class name for each file that ends in
       (errors are considered failures as well). Overrides value set in &lt;junit&gt;</td> 
     <td align="center" valign="top">No.</td>
 </tr>
+  <tr>
+    <td valign="top">filtertrace</td> 
+    <td valign="top">Filter out junit and ant stack frames from error and failure stack 
+    traces.  Overrides value set in &lt;junit&gt;</td> 
+    <td align="center" valign="top">No, default is "on."</td>
+  </tr>
   <tr>
     <td valign="top">todir</td> 
     <td valign="top">Directory to write the reports to.</td>
@@ -371,9 +388,21 @@ test is run in a separate VM. If a test fails, the build process is
 aborted. Results are collected in files named
 <code>TEST-<em>name</em>.txt</code> and written to <code>${reports.tests}</code>.</p>
 
-<p>By using the errorProperty and failureProperty tags, it is possible to
+<p>By using the errorProperty and failureProperty attributes, it is possible to
 perform setup work (such as starting an external server), execute the test,
 clean up, and still fail the build in the event of a failure.</p>
 
+<p>The filtertrace attribute condenses error and failure stack traces before reporting them.
+It works with the plain and xml formatters.  It filters out lines that begin with the following 
+string patterns:<pre>
+   "junit.framework.TestCase"
+   "junit.framework.TestResult"
+   "junit.framework.TestSuite"
+   "junit.framework.Assert."
+   "junit.swingui.TestRunner"
+   "junit.awtui.TestRunner"
+   "junit.textui.TestRunner"
+   "java.lang.reflect.Method.invoke("
+   "org.apache.tools.ant."</pre></p> 
 </body>
 </html>