ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r564630 - /ant/core/branches/ANT_17_BRANCH/docs/ant_in_anger.html
Date Fri, 10 Aug 2007 15:49:28 GMT
Author: peterreilly
Date: Fri Aug 10 08:49:27 2007
New Revision: 564630

sync with trunk


Modified: ant/core/branches/ANT_17_BRANCH/docs/ant_in_anger.html
--- ant/core/branches/ANT_17_BRANCH/docs/ant_in_anger.html (original)
+++ ant/core/branches/ANT_17_BRANCH/docs/ant_in_anger.html Fri Aug 10 08:49:27 2007
@@ -841,13 +841,6 @@
 <a href="">XDoclet</a> only run under Ant, because
 that is the right place to be.
-<!-- <dt><b>
-Use Antidote as the invocation tool
-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. 
- -->
 Use the replace task to programmatic modify text files in your project.  
@@ -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:
For additional commands, e-mail:

View raw message