Author: jhm
Date: Wed Jul 18 04:47:36 2007
New Revision: 557235

URL: http://svn.apache.org/viewvc?view=rev&rev=557235
Log:
Remove Antidote notes.

Modified:
    ant/core/trunk/docs/ant_in_anger.html

Modified: ant/core/trunk/docs/ant_in_anger.html
URL: 
http://svn.apache.org/viewvc/ant/core/trunk/docs/ant_in_anger.html?view=diff&rev=557235&r1=557234&r2=557235
==============================================================================
--- ant/core/trunk/docs/ant_in_anger.html (original)
+++ ant/core/trunk/docs/ant_in_anger.html Wed Jul 18 04:47:36 2007
@@ -841,13 +841,6 @@
 <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 @@
 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>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to