On Tue, 2003-10-07 at 10:28, Christopher Lenz wrote: > there is a rather serious problem with the implementation of the CactifyWar > task: it will read the content of the entire WAR into memory to be able to > analyze whether it needs to add the cactus JARs. Thus if your WAR is very > large, it could be possible for the task to run out of memory. I wanted to > have this issue addressed quite some time ago, but haven't had the time (and > maybe not the skill ;-P ) so far. > > 'tis pretty weird that the exception is thrown from Project.executeTarget > though. Maybe the nested exception gives the exact location where we're > running out of memory? (I suspect it to be the WarArchive class).
Hum. That must be the issue, as the WAR is roughly 44M (yeah, it's a big app). As far as the nested exception goes....what you see is what I get. And that's running ant -v. So, is there a workaround for this (besides shutting down other apps to free up memory space)? Thanks b
signature.asc
Description: This is a digitally signed message part
