ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: jakarta-ant/docs/manual/CoreTasks antcall.html
Date Wed, 08 Aug 2001 12:09:08 GMT
conor       01/08/08 05:09:08

  Modified:    docs/manual/CoreTasks antcall.html
  Clarify what happens in an antcall and why some targets are
  evaluated twice
  Submitted by:	Steve Loughran <>
  Revision  Changes    Path
  1.4       +8 -0      jakarta-ant/docs/manual/CoreTasks/antcall.html
  Index: antcall.html
  RCS file: /home/cvs/jakarta-ant/docs/manual/CoreTasks/antcall.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- antcall.html	2001/07/20 10:07:35	1.3
  +++ antcall.html	2001/08/08 12:09:08	1.4
  @@ -21,6 +21,14 @@
   <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>
  +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>
  +"doSomethingElse" will call "init" during the call. Of course, any properties defined in
  +antcall task or inherited from the calling target will be fixed and not overridable
  +in the init task -or indeed in the "doSomethingElse" task.  
   <table border="1" cellpadding="2" cellspacing="0">

View raw message