ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From peterrei...@apache.org
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

URL: http://svn.apache.org/viewvc?view=rev&rev=564630
Log:
sync with trunk

Modified:
    ant/core/branches/ANT_17_BRANCH/docs/ant_in_anger.html

Modified: ant/core/branches/ANT_17_BRANCH/docs/ant_in_anger.html
URL: http://svn.apache.org/viewvc/ant/core/branches/ANT_17_BRANCH/docs/ant_in_anger.html?view=diff&rev=564630&r1=564629&r2=564630
==============================================================================
--- 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="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: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message