Hi Bram, thanks for your reply.
Yes, I did.

I tried  with

-Xmx1024m -Xms512m and with

-Xmx1024m -Xms512m -XX:PermSize=128m -XX:MaxPermSize=256m

as I find in another thread, but it still not work.

I set them from command line and I also tried to modify the mvn.bat file too
.. still the same error ..

Also, to compile the previous version  I was using 512m. Now, with only 80
class more it seems that 1gb is not enought :-((.

It seems than even if there are these options, the compiler doesn't see ..

Regards
Pier.




On 5/22/07, Bram de Kruijff <[EMAIL PROTECTED]> wrote:

Hi Pier,

> The system is out of resources.
> Consult the following stack trace for details.
> java.lang.OutOfMemoryError

not sure about the mem settings for the compiler plugin, but my
OutOfMemoryError problems disappeared when I set the MAVEN_OPTS
environment
variable.

eg.

MAVEN_OPTS="-Xmx1024m -Xms512m"
export MAVEN_OPTS


regards,
Bram

> -----Original Message-----
> From: Pier Mauro Vignati [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 22, 2007 3:36 PM
> To: [email protected]
> Subject: Maven2 compiler out of memory error
>
> Hi,
>  I've a problem when I'm trying to compile a new version of
> my application.
>
> fooApp_1.0 has 1905 files, and Maven compiles it right
> dooApp_1.1 has 1985 files, and whenI try to compile it with
> Maven (btw, when compiling with Eclipse works fine), I'm
> receive  the following error:
>
> org.apache.maven.BuildFailureException : Compilation failure
> Failure executing javac,  but could not parse the error:
>
> The system is out of resources.
> Consult the following stack trace for details.
> java.lang.OutOfMemoryError
>
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> DefaultLifecycleExecutor.java:5
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoa
> lWithLifecycle
> (DefaultLifecycleExe
> or.java :480)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
> DefaultLifecycleExecutor.java:45
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoa
> lAndHandleFailures(DefaultLifecycl
>
> ecutor.java:311)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTas
> kSegments
> (DefaultLifecycleExecutor
> va:278)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
> DefaultLifecycleExecutor.java :143)
>         at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>         at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke (
> DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java
> :315)
>         at org.codehaus.classworlds.Launcher.launch
> (Launcher.java:255)
>         at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java
> :430)
>         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>
>
> In my pom.xml I'd configured the JDK as:
>             <plugin>
>                 <groupId>org.apache.maven.plugins</groupId>
>                 <artifactId>maven-compiler-plugin</artifactId>
>                 <version> 2.1-SNAPSHOT</version>
>                 <configuration>
>
> <executable>${JAVA_1_4_HOME}/bin/javac</executable>
>                     <fork>true</fork>
>                     <source> 1.4</source>
>                     <target>1.4</target>
>                     <meminitial>128m</meminitial>
>                     <maxmem>1024m</maxmem>
>                     <verbose>false</verbose>
>                 </configuration>
>             </plugin>
>
> (I got the same error with version 2.0.2 and 2.0.1)
>
>
> I've also an drt watson file, with
> # An unexpected error has been detected by HotSpot Virtual Machine:
> #
> #  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x080c15d5,
> pid=896, tid=3920 # # Java VM: Java HotSpot(TM) Client VM
> (1.4.2_12-b03 mixed mode) # Problematic frame:
> # V  [jvm.dll+0xc15d5]
> #
> ......
> VM Arguments:
> jvm_args: -Dapplication.home=C:\Java\1.4.2_12 -Xms8m
> -Xmx1224m -Xms512m
> java_command:
> [EMAIL PROTECTED]:/Temp/org.codehaus.plexus.compiler.
> javac.JavacCompiler54296arguments
> Launcher Type: SUN_STANDARD
> .................................................................
>
> Any idea ?
>
> Regards
> Pier.
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to