clarify where addConfigured plays into the task's life-cycle.

git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@910244 13f79535-47bb-0310-9956-ffa450edef68

docs/manual/develop.html

@@ -106,7 +106,9 @@ good convention, though.</p>
   <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 @@ good convention, though.</p>
   <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