[mule-dev] mvn -DskipTests install -- results in "java.lang.OutOfMemoryError: Java heap space"

43 views
Skip to first unread message

richrem

unread,
Feb 6, 2009, 4:43:26 PM2/6/09
to d...@mule.codehaus.org

I am following the instructions found on
http://www.mulesource.org/display/MULECDEV/Building+from+Source

I am using a Mac with the following environment:
- Maven version: 2.0.9
- Java version: 1.5.0_16
- OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix"

I did the following:

$ svn co http://svn.codehaus.org/mule/tags/mule-2.1.2
...
Checked out revision 13974.
$ cd mule-2.1.2
$ mvn -DskipTests install

[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Mule ESB
[INFO] Mule Build Tools
[INFO] 3rd-party libs repackaged for OSGi
...
[INFO] [bundle:bundle]
[WARNING] Warning building bundle
commons-beanutils:commons-beanutils.osgi:bundle:1.7.0 : There are split
packages, use directive -split-package:=(merge-first|merge-last) on
instruction to get rid of this warning: , classpath: [Jar:.,
Jar:commons-beanutils, Jar:commons-logging] from:
/Users/Rich/.m2/repository/commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar
[WARNING] Warning building bundle
commons-beanutils:commons-beanutils.osgi:bundle:1.7.0 : There are split
packages, use directive -split-package:=(merge-first|merge-last) on
instruction to get rid of this warning: META-INF, classpath: [Jar:.,
Jar:commons-beanutils, Jar:commons-logging] from:
/Users/Rich/.m2/repository/commons-logging/commons-logging/1.0.3/commons-logging-1.0.3.jar
[WARNING] Warning building bundle
commons-beanutils:commons-beanutils.osgi:bundle:1.7.0 : Instructions for
Private-Package that are never used: edu\..*|edu, com\..*|com,
javax\..*|javax, 1\.0.*, net\..*|net
...
[INFO]
------------------------------------------------------------------------
[INFO] Building Mule Core
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
[INFO] [enforcer:enforce {execution: enforce-maven-version}]
[INFO] [enforcer:enforce-once {execution: enforce-maven-version}]
[INFO] [buildnumber:create {execution: default}]
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: 13974 at timestamp: 2009-Feb-06 13:19:57
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 675 source files to
/Users/Rich/dev/projects/oss/mule-2.1/mule-2.1.2/core/target/classes
[INFO]
------------------------------------------------------------------------
[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
at com.sun.tools.javac.code.Scope.dble(Scope.java:150)
at com.sun.tools.javac.code.Scope.enter(Scope.java:185)
at com.sun.tools.javac.comp.MemberEnter.importAll(MemberEnter.java:129)
at com.sun.tools.javac.comp.MemberEnter.visitTopLevel(MemberEnter.java:504)
at com.sun.tools.javac.tree.Tree$TopLevel.accept(Tree.java:382)
at com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:383)
at com.sun.tools.javac.comp.MemberEnter.complete(MemberEnter.java:778)
at com.sun.tools.javac.code.Symbol.complete(Symbol.java:355)
at com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:612)
at com.sun.tools.javac.comp.Enter.complete(Enter.java:467)
at com.sun.tools.javac.comp.Enter.main(Enter.java:445)
at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:404)
at com.sun.tools.javac.main.Main.compile(Main.java:592)
at com.sun.tools.javac.main.Main.compile(Main.java:544)
at com.sun.tools.javac.Main.compile(Main.java:85)
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.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:420)
at
org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:141)
at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:493)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)

=== end of stack trace ===

So, I have these questions:

1) What's the best way around this?

2) Should I ignore the [WARNING] messages shown above? BTW, there were
other [WARNING] logs, which I can post if desired.

3) Are [WARNING] logs expected during a mvn install?

TIA,
Rich

--
View this message in context: http://www.nabble.com/mvn--DskipTests-install----results-in-%22java.lang.OutOfMemoryError%3A-Java-heap-space%22-tp21881234p21881234.html
Sent from the Mule - Dev mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email


Andrew Perepelytsya

unread,
Feb 6, 2009, 4:48:53 PM2/6/09
to d...@mule.codehaus.org
Reply all
Reply to author
Forward
0 new messages