Looks like John made this change in revision 585914. Comments from the commit are
"WODEN-67 Changed Woden Ant and Maven builds to create 3 separate jar files (api, dom and om) instead of a single jar file." John - Can you shed some light on why you made the fork="yes" change before it gets reverted? Lawrence "Jeremy Hughes" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 03/12/2008 05:57 PM Please respond to [email protected] To [email protected] cc Subject Re: junit fork Hmm, can't think of one. If no-one has objections I'll change to 'no' Cheers, Jeremy On 12/03/2008, Sudhir V <[EMAIL PROTECTED]> wrote: > > 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 homepage. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
