John Embretsen wrote:
Bryan Pendleton wrote:
I too get a few OutOfMemoryErrors when I run "ant junitreport" with
default settings. They disappear if I tell ant to increase the max
heap memory to some high value. So far I have not been able to do
that from the command line, so I edited the "junit-core" target in
build.xml instead:
Thanks John! That's very helpful.
Does this seem like a reasonable change to make permanent? It would
certainly be nice to be able to run "ant junitreport" more reliably.
Although I would like to know more about why some of the junit suites
require extra memory, I think it would save developers lots of hassle
in the mean while if we check in this change.
It may be related to DERBY-2344, statements staying in the cache even
after the table on which they depend is dropped.
https://issues.apache.org/jira/browse/DERBY-2344
Kathey
