For everyone else following this thread, the reason you need to use the "argLine" rather than MAVEN_OPTS is that tests are forked so they run in their own JVM. Setting MAVEN_OPTS sets the heap limit for the JVM running Maven, but not the JVM running the tests. The "argLine" configuration sets additional arguments for the JVM that is running the tests.
-----Original Message----- From: Dave Hoffer [mailto:[EMAIL PROTECTED] Sent: Thursday, May 11, 2006 21:55 To: Maven Users List Subject: RE: [m2.0.4] OutOfMemoryError Dan, I think you are right! I just added this to one of the failing projects and it works. For me maven is ignoring the MAVEN_OPTS setting. Using 'argLine' my memory usage is now reported to be >300MB where it was stuck just shy of 64MB. Thanks a bunch. -dh -----Original Message----- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Thursday, May 11, 2006 4:47 PM To: users@maven.apache.org Cc: Kris Nuttycombe Subject: Re: [m2.0.4] OutOfMemoryError You can use the "argLine" configuration option for surefire plugin to add JVM args. Things like "-ea" to enable the assertions that you should be testing are also good things to put on that line. Dan On Thursday 11 May 2006 16:40, Kris Nuttycombe wrote: > I have a related question to this: Is it possible to specify the memory > footprint except using the MAVEN_OPTS environment variable? It would be > useful to have this as an option for the surefire plugin, at least if > the tests are running in a separate JVM. > > Kris > > Dave Hoffer wrote: > >For some of my projects that use a lot of memory when running unit > > tests I set MAVEN_OPTS to -Xmx1024m to get all the tests to not throw > > OutOfMemoryErrors. > > > >I now have a maven project that has a dependency on the prior > > component but I do get an OutOfMemoryError when I run the unit tests. > > I have tried to set -Xmx to larger values with no success, as it > > always fails. The poms are all but identical, why should one fail? > > > >Also, in the process viewer I see that when running the tests there > > are two java processes. One reports using about 90MB and the other > > about 64MB. Why are there two? These numbers are way lower than the > > max java heap size specified. > > > >Any ideas? > > > >-dh > > > >--------------------------------------------------------------------- > >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] -- J. Daniel Kulp [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] This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
