As per build.xml under the root directory, the junit tests are run by forking a
seperate JVM (via the fork property). I would get a "out of memory exception"
since enough heap memory could not be set aside for JVM and playing around with
java options like -Xms and -Xmx did not help. My RAM size was 1GB. Maximizing
Virtual memory and -Xmx value did not help.
The only way I could run the woden junit tests was by not forking a seperate
JVM (set fork property to "no").
Is there a specific reason for setting fork property to "yes" when the woden
junit test could be run in the parent JVM itself
sudhir
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
