From abfdb4af34fa54587dcbe5008c23a94a4e3035c9 Mon Sep 17 00:00:00 2001
From: Simon Kitching <skitching@apache.org>
Date: Mon, 27 Feb 2006 02:31:40 +0000
Subject: [PATCH] * Make LogKit lib available to unit tests * Fix minor
 documentation error re running specific tests * Add documentation on enabling
 diagnostics during tests * replace tabs with spaces

git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk@381230 13f79535-47bb-0310-9956-ffa450edef68
---
 build.xml | 30 ++++++++++++++++++------------
 1 file changed, 18 insertions(+), 12 deletions(-)

diff --git a/build.xml b/build.xml
index 3ee7adb..a3d0bac 100644
--- a/build.xml
+++ b/build.xml
@@ -62,7 +62,7 @@
   <!--
     - The names of the unit tests to run. By default all tests are run, but
     - this can be overridden from the command line by something like:
-    -   ant -Dtestmatch=**/FooTestCase.java testall
+    -   ant -Dtestmatch=**/FooTestCase test
     -->
   <property name="testmatch" value="**/*TestCase"/>
 
@@ -202,6 +202,7 @@
   <property name="test.sysprops.testclasses" value="${build.home}/tests"/>
   <property name="test.sysprops.log4j12" value="${log4j12.jar}"/>
   <property name="test.sysprops.log4j13" value="${log4j13.jar}"/>
+  <property name="test.sysprops.logkit" value="${logkit.jar}"/>
   <property name="test.sysprops.servletapi" value="${servletapi.jar}"/>
   <property name="test.sysprops.commons-logging" value="${build.home}/${core.jar.name}"/>
   <property name="test.sysprops.commons-logging-api" value="${build.home}/${api.jar.name}"/>
@@ -714,22 +715,27 @@ This configuration is typically used to create a release only.
       <!-- 
         - Provide a set of properties pointing to the logging libs for
         - the use of the PathableClassLoader class used by some unit tests.
-	-->
+        -->
       <syspropertyset refid="test-lib-props"/>
       <classpath refid="test.classpath"/>
 
+      <!--
+        - Uncomment this to enable logging diagnostics for tests
+        - <jvmarg value="-Dorg.apache.commons.logging.diagnostics.dest=STDERR"/>
+        -->
+
       <!--
         - Auto-detect the tests to run. Checking the ${build.home}/tests
-	- directory for .class files rather than the src/test directory
-	- for .java files means that when we run the tests on platforms
-	- where some components (eg jdk14 logging) is not available, 
-	- just ensuring the tests are skipped from the compile will
-	- also cause them to be skipped from the testing.
-	-
-	- This does introduce the danger that if tests accidentally
-	- fail to compile then we won't notice it here. However that
-	- should have been reported earlier anyway.
-	-->
+        - directory for .class files rather than the src/test directory
+        - for .java files means that when we run the tests on platforms
+        - where some components (eg jdk14 logging) is not available, 
+        - just ensuring the tests are skipped from the compile will
+        - also cause them to be skipped from the testing.
+        -
+        - This does introduce the danger that if tests accidentally
+        - fail to compile then we won't notice it here. However that
+        - should have been reported earlier anyway.
+        -->
       <batchtest todir="${build.home}/test-reports">
         <fileset dir="${build.home}/tests">
           <include name="${testmatch}.class"/>