Jake, I did try this however the problem is that all taskdefs are copied over too. :-\ Is there a way around this?
Cheers, --Bill On Tue, 30 Nov 2004 23:44:26 -0600, Jacob Kjome <[EMAIL PROTECTED]> wrote: > At 10:09 AM 11/30/2004 -0800, you wrote: > >Jake, > > > >I tried doing that via <ant> but it didn't really work -- IOW, it > >didn't reinitialize. Should I use antcall instead? What's the > >difference? > > Did you set <ant> so that properties and references don't get > propagated? See the Ant task manual for info on what attributes you need > to set to do this. <ant> is actually the way to go here. It if doesn't > work with <ant> (properly configured), it almost certainly won't work with > <antcall>. > > Jake > > > > > > >Thanks, > >--Bill > > > > > >On Mon, 29 Nov 2004 23:36:35 -0600, Jacob Kjome <[EMAIL PROTECTED]> wrote: > >> > >> Does it work if you use <antcall> and (re)initialize the taskdef within > the > >> <antcall>? > >> > >> Jake > > > >--------------------------------------------------------------------- > >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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
