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 but
At 10:09 AM 11/30/2004 -0800, you wrote:
>Jake,
>
>I tried doing that via but it didn't really work -- IOW, it
>didn't reinitialize. Should I use antcall instead? What's the
>difference?
Did you set so that properties and references don't get
propagated? See the Ant task manual for info on what
Jake,
I tried doing that via but it didn't really work -- IOW, it
didn't reinitialize. Should I use antcall instead? What's the
difference?
Thanks,
--Bill
On Mon, 29 Nov 2004 23:36:35 -0600, Jacob Kjome <[EMAIL PROTECTED]> wrote:
>
> Does it work if you use and (re)initialize the taskdef wit
Does it work if you use and (re)initialize the taskdef within the
?
Jake
At 09:14 AM 11/29/2004 -0800, you wrote:
>All,
>
>I discovered recently that it's pretty much impossible to run the JSPC
>task more than once. Others have had this issue before (I researched
>the list a bit) and it seems li
All,
I discovered recently that it's pretty much impossible to run the JSPC
task more than once. Others have had this issue before (I researched
the list a bit) and it seems like it's more of a taskdef problem. The
issue is this:
... dynamic path elements here like so: ...
