I'm not aware of any direct source of out of memory problems in the 1.1 code
and I'm running 1.1 trunk based builds for months.
But we're having a quite huge build script and prior to introducing svnAnt
we had to set up the ANT_OPTS=-Xmx??? to prevent the OofM.
I might try to look for possible memory consumption increase in 1.1. but you
should set the ANT_OPTS until I'll find something.
Regarding the jars, of course they're not needed all all the time.
(javasvn and ganymed are necessary in case you want to use JavaSVN,
svnjavahl is for JavaHL. Just the svnClientAdapters is a must all the time).
From: Jerry Brown [mailto:firstname.lastname@example.org]
Sent: Friday, November 03, 2006 5:52 PM
Subject: [Subclipse-users] Svnant 1.1-RC2 - Java heap space issues
I have been trying to use the svnant-1.1.0-RC2 task, due to recent update to
Subversion 1.4, which broke us when using svnant-1.0.0. I am getting build
failures due to running out of heap space when using the new version. This
happens whether I set the javahl attribute to true or false (initially
thought it might be javahl that was the problematic part). It is happening
on both Windoze 2003 Server and Mac OS X 10.4.8. Both machines are running
Java 1.5, Ant 1.6.5. The only thing that was changed in the build script was
that I pointed the path to the new version of svnant and changed the taskdef
for 1.0.0 to a typedef for 1.1.0-RC2 . BTW, the readme.txt needs to reflect
the change in resource path and change from taskdef to typedef for version
Short of having to go mess with everybody's Ant heap settings, is there
possibly something in the coding (lots of debug code, etc) or the packages
used which I might be causing this? I notice a couple of new jars in this
version. Are they all needed? What if I just want to use JavaSVN and not
JavaHL, or vice verse, would all the jars be needed?
Thanks in advance for a quick response, I am kind of dead in the water, had
not anticipated this, unfortunately.
Received on Mon Nov 6 08:59:24 2006