I do this: maven.junit.fork = true maven.junit.jvmargs = -Xmx1024m
> -----Original Message----- > From: Marthi, Bhaskar [mailto:[EMAIL PROTECTED] > Sent: 22 June 2004 16:05 > To: 'Maven Users List' > Subject: RE: Multiproject:site OutOfMemory > > Matt, > How do you force forking VM. The plugin does not seem to > support such an option. Can you please elaborate a little > more for my benefit? > > Thanks, > Bhaskar > > > The information contained in this communication may be > confidential or > legally privileged and is intended only for the recipient > named above. If the reader of this message is not the > intended recipient, you are hereby notified that any > dissemination, distribution or copying of this communication > or its contents is strictly prohibited. If you have received > this communication in error, please immediately advise the > sender and delete the original and any copies from your > computer system. > > > > > -----Original Message----- > From: Matt Read [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 22, 2004 5:56 AM > To: 'Maven Users List' > Subject: RE: Multiproject:site OutOfMemory > > > > > > > 3. I seem to have temporarily resolved my issue by doing > > > > the following > > > > > but my susispicion is that it will come back as my > > codebase grows. > > > > > a) disabling all JDepend reports (I've had lots of > > > > problems with > > > > > OutOfMemory errors and Jdepend runnning from Ant in the past) > > > > > b) forking the JVM while the Junit tests run > > > > > c) separating removing any other goals from the build > > > > so that I'm > > > > > only running multiproject:site. > > > > > > > > Does turning any of the above back 'on' cause the failure again? > > > > > > Yes, the failure is reproducable, would it be useful for > > you to know > > > exactly which if these options might trigger it? > > > > Definitely. If it's JDepend helping out, or the junit tests > would be > > useful. > > > > I reversed all my changes and eventually could reproduce the > problem only by switching off forking of the JWebUnit tests. > It seems that there's a substantial memory leak there. I'll > look into it further but my builds are all happy again for > now. Thanks all for your help and suggestions. > > Matt. > > > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
