Author: bodewig
Date: Mon Feb 15 16:04:24 2010
New Revision: 910244
URL: http://svn.apache.org/viewvc?rev=910244&view=rev
Log:
clarify where addConfigured plays into the task's life-cycle.
Modified:
ant/core/trunk/docs/manual/develop.html
Modified: ant/core/trunk/docs/manual/develop.html
URL:
http://svn.apache.org/viewvc/ant/core/trunk/docs/manual/develop.html?rev=910244&r1=910243&r2=910244&view=diff
==============================================================================
--- ant/core/trunk/docs/manual/develop.html (original)
+++ ant/core/trunk/docs/manual/develop.html Mon Feb 15 16:04:24 2010
@@ -106,7 +106,9 @@
<li>All child elements of the XML element corresponding to this task
are created via this task's <code>createXXX()</code> methods or
instantiated and added to this task via its <code>addXXX()</code>
- methods, at run time.</li>
+ methods, at run time. Child elements corresponding
+ to <code>addConfiguredXXX()</code> are created at this point but
+ the actual <code>addCondifgired</code> method is not called.</li>
<li>All attributes of this task get set via their corresponding
<code>setXXX</code> methods, at runtime.</li>
@@ -118,6 +120,10 @@
<li>All attributes of all child elements get set via their corresponding
<code>setXXX</code> methods, at runtime.</li>
+ <li>If child elements of the XML element corresponding to this task
+ have been created for <code>addConfiguredXXX()</code> methods,
+ those methods get invoked now.</li>
+
<li><a name="execute"><code>execute()</code></a> is called at runtime.
If <code>target1</code> and <code>target2</code> both depend
on <code>target3</code>, then running
