From d62e0058ee50a086e304af1fb931ecff9d6f6c01 Mon Sep 17 00:00:00 2001 From: Matthew Jason Benson Date: Tue, 24 Jan 2006 20:14:49 +0000 Subject: [PATCH] sp git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@372007 13f79535-47bb-0310-9956-ffa450edef68 --- docs/antlibs/antunit/index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/antlibs/antunit/index.html b/docs/antlibs/antunit/index.html index c1ef5e7dc..29c90ddea 100755 --- a/docs/antlibs/antunit/index.html +++ b/docs/antlibs/antunit/index.html @@ -115,7 +115,7 @@

Initially all tests for Ant tasks were written as individual JUnit test cases. Pretty soon it was clear that most tests needed to perform common tasks - like reading a build file, intializing a project instance with + like reading a build file, initializing a project instance with it and executing a target. At this point BuildFileTest was invented, a base class for almost all task test cases.

BuildFileTest works fine and in fact has been picked up by the Ant-Contrib Project @@ -249,7 +249,7 @@ public class ANTLRTest extends BuildFileTest { relays test results to them.

Currently only a single implementation <plainlistener> modelled after the "plain" - JUnit listener is bundeled with the library.

+ JUnit listener is bundled with the library.

Examples