ion but it
still does incurr the memory impact.
The downside is that s cannot be included in a 'depends' attribute.
Later,
Ninju
- Original Message
From: Dharmesh Vyas <[EMAIL PROTECTED]>
To: Ant Users List
Sent: Wednesday, February 21, 2007 1:44:00 PM
Subject: Re:
I believe ant contrib. has an "antcallback" task (or something like
that) that might accomplish what you are looking for.
Ben
-Original Message-
From: Dharmesh Vyas [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 21, 2007 2:44 PM
To: Ant Users List
Subject: Re: visibil
Thanks for your reply Ben and Antoine.
Ben: In my case what I am planning to implement, I won't be able to use
'depends'.
So, prob. I will have to use a work around of writing down the values to
some file. But, still I am wondering if I could find out some other option.
Thanks,
- Dharmesh.
On
Hello Dharmesh,
properties set in an antcall are not visible when the antcall returns.
antcall (and ant) generate new tables of properties and reference ids.
Regards,
Antoine
Original-Nachricht
Datum: Wed, 21 Feb 2007 16:57:41 +0100
Von: "Dharmesh Vyas" <[EMAIL PROTECTED]>
An
Antcall is a task that is used to call a sub project. In other words,
what is called using Antcall is a sub process in its own scope and
properties set in that scope do not come back to the calling scope. You
should see a massive increase in memory as well with ancall as it is
creating a whole ne
