I'm still having problems with anything that
resembles antcall (i.e. <foreach>) because I'm
running out of memory. So my solution to this
is to try to adapt the <foreach> task so that
it is itself a tasknester (like <if> for example)
- rather than calls another target and suffers
from the same problems as <antcall>.
However I kind of consider this to be the most
sensible thing <foreach> can do anyway which
leads me to be slightly suspicious as to why this
wasn't done. Is it due to a good reason that
<foreach> has been implemented so that it has
to call a task (which it may well be), or is it
just because it was implemented that way first
of all and its stuck like that?
I'd appreciate any response/suggestions as I
dont want to start something which I'm unable to
do because of a reason that was already known by
one of you clever bods months ago.
Incidentally another question- if I changed it
to allow both to happen, would ant-contrib be
interested in it? Or should I just keep my little
endeavours to myself?
Thanks for all your help
Get latest updates about Open Source Projects, Conferences and News.