I read about the new macrodef task which can be used create a custom composite task by combining other tasks together. Using the macrodef task instead of antcall cant we overcome the performance overhead and the property visibility issues with antcall?
--- On Thu, 8/19/10, Knuplesch, Juergen <[email protected]> wrote: From: Knuplesch, Juergen <[email protected]> Subject: AW: Conditional target problem To: "Ant Users List" <[email protected]> Date: Thursday, August 19, 2010, 8:03 AM Antcallback gives back some props you define -----Ursprüngliche Nachricht----- Von: Niklas Matthies [mailto:[email protected]] Gesendet: Mittwoch, 18. August 2010 15:55 An: Ant Users List Betreff: Re: Conditional target problem On Tue 2010-08-17 at 16:20h, Vimil Saju wrote on user: > I know ant is supposed to be declarative language as opposed to a > procedural one, but whats wrong with using the 'if' task provided > with ant-contrib along with "ant-call" task? AntCall effectively creates a new Ant instance. Properties and references set within the call won't be visible after the call returns, and targets executed before the call might be executed again within the call. It's very different from having a target as a dependency. Replacing one with the other has all sorts of ramifications. -- Niklas Matthies --------------------------------------------------------------------- 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]
