Author: snoopdave
Date: Fri Jul 20 08:12:24 2007
New Revision: 558017
URL: http://svn.apache.org/viewvc?view=rev&rev=558017
Log:
Commenting out JUnit workaround for now. We need a version of the JUnitTask
that can be configured to use our JUnit jar, otherwise test will fail on build
servers that don't have JUnit 4.1. Kohsuke's <junit2> tasks might be the ticket.
Modified:
roller/trunk/apps/weblogger/build.xml
Modified: roller/trunk/apps/weblogger/build.xml
URL:
http://svn.apache.org/viewvc/roller/trunk/apps/weblogger/build.xml?view=diff&rev=558017&r1=558016&r2=558017
==============================================================================
--- roller/trunk/apps/weblogger/build.xml (original)
+++ roller/trunk/apps/weblogger/build.xml Fri Jul 20 08:12:24 2007
@@ -47,10 +47,12 @@
<available file="./build/webapp/WEB-INF/dbscripts/derby/createdb.sql"
property="dbscripts-exist" />
- <!-- Ensure JUnit is defined even if not installed in Ant -->
+ <!-- Ensure JUnit is defined even if not installed in Ant.
+ We need a version of JUnitTask that doesn't load junit from ant/lib.
<taskdef name="junit"
classpath="${ro.tools}/buildtime/junit-4.1.jar"
classname="org.apache.tools.ant.taskdefs.optional.junit.JUnitTask" />
+ -->
<target name="usage" description="Print usage for key targets">
