One unfortunate side affect (to me) of the antcall task is that properties set in the called task are available only within the scope of the antcall. I originally figured that since the task being called was within the same project, the properties would have project scope.
brian peterson | -----Original Message----- | From: Stefan Bodewig [mailto:[EMAIL PROTECTED]] | Sent: Thursday, November 29, 2001 8:51 AM | To: [EMAIL PROTECTED] | Subject: Re: antcall documentation confusion | | | On Thu, 29 Nov 2001, Steve Cohen <[EMAIL PROTECTED]> wrote: | | > Several times within this documentation, the "project" is referred | > to. | | It should be something like "execution context" or similar. You can | execute the same project/buildfile more than once and <antcall> | executes the given target within a new "context". | | Am I making sense? | | Stefan | | -- | To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
