Browse Source

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
master
Conor MacNeill 24 years ago
parent
commit
c8691cff5b
1 changed files with 8 additions and 0 deletions
  1. +8
    -0
      docs/manual/CoreTasks/antcall.html

+ 8
- 0
docs/manual/CoreTasks/antcall.html View File

@@ -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 <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 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> 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> <h3>Parameters</h3>
<table border="1" cellpadding="2" cellspacing="0"> <table border="1" cellpadding="2" cellspacing="0">
<tr> <tr>


Loading…
Cancel
Save