You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ant.apache.org by bu...@apache.org on 2003/11/15 00:22:14 UTC

DO NOT REPLY [Bug 24720] - repeated cause OutOfMemeory exception

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24720>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24720

repeated <antcall/> cause OutOfMemeory exception

gudnabrsam@yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From gudnabrsam@yahoo.com  2003-11-14 23:22 -------
This is a known limitation of <antcall>, the reason being that it creates a new 
project for each invocation.  The first workaround, historically, would be to 
use the -X options to your JVM to increase available memory.  In Ant 1.6,  
<macrodef> and <presetdef> address some of the requirements that might lead one 
to use <antcall> in the first place.  Also see Dale Anson's Antelope project at 
sourceforge.net for some <antcall> variants.

Most likely this bug is a duplicate of some other, as well.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org