But each developer would have to manually set that each time. Not ideal in that respect. Can't you configure this in the pom?

dan tran wrote:
set MAVEN_OPTS environment variable to increase of memory ;-)

-D


On 3/17/06, Erik van Zijst <[EMAIL PROTECTED]> wrote:

Guys,

I'm compiling a lot of (partially generated) sources, causing the
compiler to give an OutOfMemoryError:


[EMAIL PROTECTED] geminix-session]$ mvn compile
[INFO] Scanning for projects...
...
[ERROR] BUILD FAILURE
[INFO]

----------------------------------------------------------------------------
[INFO] 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: Java heap space
...


I could find any memory properties for maven-compiler-plugin, so I tried
switching to fork=true. Unfortunately, now the compiler fails to start
at all, printing:


Compiling 2640 source files to
/home/erik/workspace/geminix-session/target/classes
[INFO]

----------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]

----------------------------------------------------------------------------
[INFO] Compilation failure

Failure executing javac,  but could not parse the error:

[INFO]

----------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.BuildFailureException: Compilation failure
       at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:552)
       at

org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
(DefaultLifecycleExecutor.java:472)
       at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
DefaultLifecycleExecutor.java:451)
       at

org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:303)
       at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:270)
       at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.java:139)
       at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
...


The only thing I changed was adding <fork>true</fork>.
Is there any way to enlarge javac's available memory with maven2?

Erik
--
U       X
e dUdX, e dX, cosine, secant, tangent, sine, 3.14159...

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





--
Simulations are like miniskirts, they show a lot and hide the essentials.
                -- Hubert Kirrman

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

Reply via email to