Thanks.
On 3/29/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
I added the jvm memory option to the surefire plugin because now I have
this pb too :(
Emmanuel
Thierry Lach a écrit :
> I agree. I don't want to have to bump up my memory config for all
projects
> just because of one.
>
> On 3/
I added the jvm memory option to the surefire plugin because now I have this pb
too :(
Emmanuel
Thierry Lach a écrit :
I agree. I don't want to have to bump up my memory config for all projects
just because of one.
On 3/23/07, Andrew Williams <[EMAIL PROTECTED]> wrote:
I think that modifyi
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 perm
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 to
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 proble
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 section of continuum's root pom.xml
org.apache.maven.plugins
maven-sur
I sometimes get that problem too, when I see it I insert the
following into the section of continuum's root pom.xml
org.apache.maven.plugins
maven-surefire-plugin
-Xmx512m
org.apache.maven.plugins
maven-compi
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
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:
http://maven.zones.apache.org
Emmanuel Venisse wrote:
how many memory is allocated to the build? Normally the default is enough.
No idea - checked out a pristine copy of trunk as of an hour or two ago,
and did an mvn install.
Is there somewhere where memory allocations are set, perhaps in a pom file?
Regards,
Graham
--
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
--
Emmanuel Venisse wrote:
jdk version?
Latest MacOSX version, jdk v1.5.0_07-164.
Regards,
Graham
--
smime.p7s
Description: S/MIME Cryptographic Signature
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:
org.apache.maven.continuum.buildcontroller.DefaultBuil
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
-
14 matches
Mail list logo
