From c8691cff5bcdaa9a86d3c2556b5add1505e9819e Mon Sep 17 00:00:00 2001
From: Conor MacNeill <conor@apache.org>
Date: Wed, 8 Aug 2001 12:09:08 +0000
Subject: [PATCH] Clarify what happens in an antcall and why some targets are
 evaluated twice

Submitted by:	Steve Loughran <steve_l@iseran.com>


git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@269519 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/CoreTasks/antcall.html | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/docs/manual/CoreTasks/antcall.html b/docs/manual/CoreTasks/antcall.html
index 50cdecbc8..2c4c94663 100644
--- a/docs/manual/CoreTasks/antcall.html
+++ b/docs/manual/CoreTasks/antcall.html
@@ -21,6 +21,14 @@ are set in the new project (See also the <a href="property.html">property task</
 <p>You can also set properties in the new project from the old project by
 using nested param tags. These properties are always passed regardless of the
 setting of <i>inheritAll</i>.  This allows you to parameterize your subprojects.</p>
+<p>
+When a target is invoked by antcall, all of its dependent targets will
+also be called within the context of any new parameters. For example. if
+the target "doSomethingElse" depended on the target "init", then the <i>antcall</i> of 
+"doSomethingElse" will call "init" during the call. Of course, any properties defined in the
+antcall task or inherited from the calling target will be fixed and not overridable
+in the init task -or indeed in the "doSomethingElse" task.  
+</p>
 <h3>Parameters</h3>
 <table border="1" cellpadding="2" cellspacing="0">
   <tr>