Oh, right, I was able to use the surefire plugin, great! Thanks heaps.
Lionel. 2009/10/8 Lionel van den Berg <[email protected]> > Thanks. It seems there are no ideal solutions but I guess I can work within > the suggestions made. Just a pain that all developers will have to configure > their own MAVEN_OPTS which ever way they choose to do it. > > Cheers > > Lionel > > > 2009/10/8 Edelson, Justin <[email protected]> > > Did you read this thread: >> http://www.nabble.com/-Maven%27s-memory--How-to-avoid-adding-the-MAVEN_OPTS-variable--td25788729.html >> >> This should answer most of your question. As for setting it on the command >> line, that's not possible AFAIK. What you can do is create multiple mvn.bat >> files which have different environment variables in them. I think this is >> primarily done with debugging (i.e. mvnDebug), but the pattern could be used >> for memory as well. >> >> Justin >> >> ________________________________ >> >> From: Lionel van den Berg [mailto:[email protected]] >> Sent: Thu 10/8/2009 12:18 AM >> To: [email protected] >> Subject: Setting Java heap space >> >> >> >> Hi all, >> >> I'm having some issues with Java heap space. To get around this I have >> added >> the line "MAVEN_OPTS=-Xmx128m" to my mvn.bat file. >> >> However, I would prefer to set it on a project by project basis or even on >> command line. Is it possible to pass it as an argument when running "mvn >> ..."? Or can it be added to the POM? I see it can be for the javadoc >> plugin. >> Ideally I only need it in the testing phase. >> >> Any help appreciated. >> >> Cheers >> >> Lionel. >> >> >> >
