<antcall> creates a new ant child context (project), this means than any properties, references set in that project will not appear in the caller project. Sometimes this is needed and sometimes not.
Alternatives are to: - set dependenices up so that this antcall is not required - use macrodefs instead of a target - use ant-contrib's <runtarget> which runs a target without creating a new project. Peter On 5/31/07, yitzle <[EMAIL PROTECTED]> wrote:
That looks like what I want. Thanks! When you are self taught multiple tools, frameworks, etc on the job its hard to look through all the components, especially something like Ant, where, as long as it works, I'm pretty happy. I did look at the list of tasks, but some of the names are not self-explanatory. Anyhow, sorry for the rant and thanks again! On 5/31/07, Qazwart <[EMAIL PROTECTED]> wrote: > Have you looked at <ant> and <antcall>? > > These allow you to call another target from inside of another target: > > <target name="num2"> > ... > <antcall target="num1"/> > </target> > > David Weintraub > [EMAIL PROTECTED] > [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
