Yeah - I finally got it, so I'll test your update.
BTW, pretty sure others have mentioned this, but it's working nicely
on my MacOS X Tiger (10.4.9) laptop.
Christian.
On Mar 29, 2007, at 11:08 AM, Emmanuel Venisse wrote:
I added the jvm memory option to the surefire plugin because now I
I think that modifying your environment or installation options is a
very bad idea,
especially if you are striving for truly reproducible build results.
Andy
On 22 Mar 2007, at 16:29, Jesse McConnell wrote:
most people I know just add the following to their environment
variables
/Test-failure-on-trunk-tf3430142.html#a9636039
Sent from the Continuum - Dev mailing list archive at Nabble.com.
ERROR!
java.lang.OutOfMemoryError: Java heap space
Not sure exactly where the JVM should be given more memory, is this a
maven problem or a continuum problem?
Regards,
Graham
--
--
View this message in context:
http://www.nabble.com/Test-failure-on-trunk-tf3430142.html
I assumed that there was a leak or something weird and that it would
get addressed.
I have certainly seen it compile and test fine without it before,
recently too, so I know it is possible...
Andy
On 22 Mar 2007, at 15:46, Thierry Lach wrote:
Any reason why this couldn't just be added
I sometimes get that problem too, when I see it I insert the
following into the build section of continuum's root pom.xml
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
configuration
Any reason why this couldn't just be added permanently?
On 3/22/07, Andrew Williams [EMAIL PROTECTED] wrote:
I sometimes get that problem too, when I see it I insert the
following into the build section of continuum's root pom.xml
plugins
plugin
most people I know just add the following to their environment variables
MAVEN_OPTS=-Xmx512m
jesse
On 3/22/07, Thierry Lach [EMAIL PROTECTED] wrote:
Any reason why this couldn't just be added permanently?
On 3/22/07, Andrew Williams [EMAIL PROTECTED] wrote:
I sometimes get that problem
Jesse McConnell wrote:
most people I know just add the following to their environment variables
MAVEN_OPTS=-Xmx512m
It shouldn't be necessary to have to patch your environment to work
around bugs in unit tests, if the tests need 512MB of RAM, then the
surefire plugin should be configured
:34 PM
To: continuum-dev@maven.apache.org
Subject: Re: Test failure on trunk
jdk version?
Graham Leggett a écrit :
Hi all,
While trying to build trunk of continuum, I am getting the following
test failure on MacosX v10.4
Hi all,
While trying to build trunk of continuum, I am getting the following
test failure on MacosX v10.4:
---
Test set:
org.apache.maven.continuum.buildcontroller.DefaultBuildControllerTest
jdk version?
Graham Leggett a écrit :
Hi all,
While trying to build trunk of continuum, I am getting the following
test failure on MacosX v10.4:
---
Test set:
Emmanuel Venisse wrote:
jdk version?
Latest MacOSX version, jdk v1.5.0_07-164.
Regards,
Graham
--
smime.p7s
Description: S/MIME Cryptographic Signature
how many memory is allocated to the build? Normally the default is enough.
Graham Leggett a écrit :
Emmanuel Venisse wrote:
jdk version?
Latest MacOSX version, jdk v1.5.0_07-164.
Regards,
Graham
--
it's set in MAVEN_OPTS env var with -Xmx and -Xms java options, but if you
don't know it, you probably use the default jvm options. You can try to it to
something like that:
MAVEN_OPTS=-Xmx256m
If you don't want to patch Continuum, you can use a prebuilt snapshot:
im not sure but i think in order to change the amount of memory the
tests can use, you have to configure the surefire plugin - changing
the amount of memory maven uses dont take effect on tests (i think
they are ran on a separate jvm)
On 3/19/07, Emmanuel Venisse [EMAIL PROTECTED] wrote:
it's
16 matches
Mail list logo
