You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by solo1970 <so...@ericsson.com> on 2009/03/16 16:43:39 UTC
Proguard plugin error! Help!
Hello,
I have an issue when I'm proguarding. Maven seems to run out of memory.
I tried increasing the memory by doing this :
setenv MAVEN_OPTS=-Xmx512M -XX:MaxPermSize=512M
But I still get the following:
[proguard] Reading library jar
[/vobs/mnr/src/src/ENR_ICS/CompilationJARs/external/wss4j-1.5.3.jar]
[proguard] Reading library jar
[/vobs/mnr/src/src/ENR_ICS/CompilationJARs/external/wstx-asl-3.2.1.jar]
[proguard] Reading library jar
[/vobs/mnr/src/src/ENR_ICS/CompilationJARs/external/xalan.jar]
[proguard] Reading library jar
[/vobs/mnr/src/src/ENR_ICS/CompilationJARs/external/xbean.jar]
[proguard] Note: duplicate definition of library class
[javax.xml.namespace.NamespaceContext]
[proguard] Note: duplicate definition of library class
[javax.xml.namespace.QName]
[proguard] Exception in thread "main" java.lang.OutOfMemoryError: Java heap
space
[proguard] at java.lang.StringCoding.trim(StringCoding.java:74)
[proguard] at java.lang.StringCoding.access$100(StringCoding.java:37)
[proguard] at
java.lang.StringCoding$CharsetSD.decode(StringCoding.java:201)
[proguard] at java.lang.StringCoding.decode(StringCoding.java:228)
[proguard] at java.lang.String.<init>(String.java:405)
[proguard] at java.lang.String.<init>(String.java:433)
[proguard] at
proguard.classfile.constant.Utf8Constant.switchToStringRepresentation(Utf8Constant.java:158)
[proguard] at
proguard.classfile.constant.Utf8Constant.getString(Utf8Constant.java:128)
[proguard] at
proguard.classfile.io.LibraryClassReader.getString(LibraryClassReader.java:318)
[proguard] at
proguard.classfile.io.LibraryClassReader.visitLibraryMember(LibraryClassReader.java:230)
[proguard] at
proguard.classfile.io.LibraryClassReader.visitLibraryClass(LibraryClassReader.java:191)
[proguard] at
proguard.classfile.LibraryClass.accept(LibraryClass.java:248)
[proguard] at proguard.io.ClassReader.read(ClassReader.java:86)
[proguard] at
proguard.io.FilteredDataEntryReader.read(FilteredDataEntryReader.java:87)
[proguard] at proguard.io.ClassFilter.read(ClassFilter.java:70)
[proguard] at proguard.io.JarReader.read(JarReader.java:67)
[proguard] at
proguard.io.DirectoryPump.readFiles(DirectoryPump.java:76)
[proguard] at
proguard.io.DirectoryPump.pumpDataEntries(DirectoryPump.java:53)
[proguard] at proguard.InputReader.readInput(InputReader.java:201)
[proguard] at proguard.InputReader.readInput(InputReader.java:175)
[proguard] at proguard.InputReader.readInput(InputReader.java:153)
[proguard] at proguard.InputReader.execute(InputReader.java:101)
[proguard] at proguard.ProGuard.readInput(ProGuard.java:195)
[proguard] at proguard.ProGuard.execute(ProGuard.java:78)
[proguard] at proguard.ProGuard.main(ProGuard.java:499)
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Obfuscation failed (result=1)
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Obfuscation failed
(result=1)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
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)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
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)
Caused by: org.apache.maven.plugin.MojoExecutionException: Obfuscation
failed (result=1)
at
com.pyx4me.maven.proguard.ProGuardMojo.proguardMain(ProGuardMojo.java:623)
at
com.pyx4me.maven.proguard.ProGuardMojo.execute(ProGuardMojo.java:476)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
... 16 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 3 minutes 32 seconds
[INFO] Finished at: Mon Mar 16 06:56:03 EDT 2009
[INFO] Final Memory: 15M/29M
[INFO]
------------------------------------------------------------------------
207.28u 2.27s 4:05.59 85.3%
Can anyone help?
Sonia
--
View this message in context: http://www.nabble.com/Proguard-plugin-error%21--Help%21-tp22540946p22540946.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Proguard plugin error! Help!
Posted by Wayne Fay <wa...@gmail.com>.
> I have an issue when I'm proguarding. Maven seems to run out of memory.
> I tried increasing the memory by doing this :
> setenv MAVEN_OPTS=-Xmx512M -XX:MaxPermSize=512M
Does this plugin execute in-process or out of process? That's the
first question to answer.
If in-process, then the MAVEN_OPTS should help resolve it. Try bumping
that to a gb or more.
If its out of process, then MAVEN_OPTS will do nothing. Some plugins
allow you to configure memory usage in the plugin. If the Proguard
plugin runs out of process and does not allow you to configure memory
usage, you might want to file as request to have it added.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org