From e3ce41867f81fa257e81e78699d19b265afbb2fe Mon Sep 17 00:00:00 2001
From: Jan Materne <jhm@apache.org>
Date: Wed, 18 Jul 2007 11:47:36 +0000
Subject: [PATCH] Remove Antidote notes.

git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@557235 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/ant_in_anger.html | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/docs/ant_in_anger.html b/docs/ant_in_anger.html
index 88fc0e0e6..0044b01c9 100644
--- a/docs/ant_in_anger.html
+++ b/docs/ant_in_anger.html
@@ -841,13 +841,6 @@ preamble and postamble work. Some projects, such as
 <a href="http://xdoclet.sf.net">XDoclet</a> only run under Ant, because
 that is the right place to be.
 
-<!-- <dt><b>
-Use Antidote as the invocation tool
-</b><dd>
-Even if you edit Ant files by hand, Antidote makes a good execution tool
-because it eliminates the startup time of the JVM, perhaps even some of
-the XML parsing delays. 
- -->
 <dt><b>
 Use the replace task to programmatic modify text files in your project.  
 </b><dd>
@@ -1020,7 +1013,7 @@ reasonable representation for programs, and text editors and source code
 management systems can all handle it nicely. But a complex Ant file can
 get ugly because XML is a bit ugly, and a complex build is, well,
 complicated. Use XML comments so that the file you wrote last month
-still makes sense when you get back to it, and use Antidote to edit the
+still makes sense when you get back to it, and use proper xml editors to edit the
 files if you prefer it. 
 
 <h3>Big projects still get complicated fast</h3>