Test runs fine in Eclpse with 256m, breaks with Maven
Good morning Mavens! Running a unittest configured with Xmx256M in Eclipse runs fine. Running the same test with Maven on the prompt with set MAVEN_OPTS=-Xmx1024m results in a Caused by: java.lang.OutOfMemoryError: Java heap space What could be the reason that running the test on the prompt results in a Java Heap Space problem (while in Eclipse it runs fine)? My configuration is Maven 3.0.3, Java jdk1.6.0_16. Thanks for commenting, Erik
Re: Test runs fine in Eclpse with 256m, breaks with Maven
How are you executing in Eclipse? How are you executing from CLI? /Anders On Fri, Sep 16, 2011 at 09:09, VanIngen, Erik (FIPS) erik.vanin...@fao.org wrote: Good morning Mavens! Running a unittest configured with Xmx256M in Eclipse runs fine. Running the same test with Maven on the prompt with set MAVEN_OPTS=-Xmx1024m results in a Caused by: java.lang.OutOfMemoryError: Java heap space What could be the reason that running the test on the prompt results in a Java Heap Space problem (while in Eclipse it runs fine)? My configuration is Maven 3.0.3, Java jdk1.6.0_16. Thanks for commenting, Erik - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Test runs fine in Eclpse with 256m, breaks with Maven
MAVEN_OPTS only affects Maven itself, not the new JVM instance it starts (by default) to run unit tests for each module. For a full-featured example of how to increase the heap of the JVM used for tests (a new one is created for each module), see the maven-surefire-plugin settings in the GeoTools root pom: http://svn.osgeo.org/geotools/trunk/pom.xml In a nutshell, you need to set your -Xmx option in plugins/plugin/configuration/argLine in your pom. Kind regards, Ben. On 16/09/11 15:09, VanIngen, Erik (FIPS) wrote: Good morning Mavens! Running a unittest configured with Xmx256M in Eclipse runs fine. Running the same test with Maven on the prompt with set MAVEN_OPTS=-Xmx1024m results in a Caused by: java.lang.OutOfMemoryError: Java heap space What could be the reason that running the test on the prompt results in a Java Heap Space problem (while in Eclipse it runs fine)? My configuration is Maven 3.0.3, Java jdk1.6.0_16. Thanks for commenting, Erik -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ExternalEmail] Re: Test runs fine in Eclpse with 256m, breaks with Maven
And the reason it might run fine in Eclipse is because you might have put -Xmx in your Eclipse JRE default JVM arguments (in Preferences). In any case, the JVM is invoked with a different classpath by Eclipse. On 16/09/11 15:59, Ben Caradoc-Davies wrote: MAVEN_OPTS only affects Maven itself, not the new JVM instance it starts (by default) to run unit tests for each module. For a full-featured example of how to increase the heap of the JVM used for tests (a new one is created for each module), see the maven-surefire-plugin settings in the GeoTools root pom: http://svn.osgeo.org/geotools/trunk/pom.xml In a nutshell, you need to set your -Xmx option in plugins/plugin/configuration/argLine in your pom. Kind regards, Ben. On 16/09/11 15:09, VanIngen, Erik (FIPS) wrote: Good morning Mavens! Running a unittest configured with Xmx256M in Eclipse runs fine. Running the same test with Maven on the prompt with set MAVEN_OPTS=-Xmx1024m results in a Caused by: java.lang.OutOfMemoryError: Java heap space What could be the reason that running the test on the prompt results in a Java Heap Space problem (while in Eclipse it runs fine)? My configuration is Maven 3.0.3, Java jdk1.6.0_16. Thanks for commenting, Erik -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven release from Git branch
Hello list! I use Git, maven-release-plugin, Hudson, and the Hudson M2 Release Plugin. Can I perform a release from a Git branch other than master? Right now, to do a release, Hudson checks out the master branch and calls mvn release:prepare release:perform. If the release succeeds, the M2 Extra Steps Plugin runs git push origin master `git tag | grep -v ^hudson` to update Git tags. If I change my Hudson config to build a different branch, like 1.2.x, will the maven-release-plugin still do the right thing? Thanks, -Stuart Sierra clojure.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: ServiceMix-4.3 examples: build using maven 2.2.1 within eclipse
[FATAL] Non-resolvable parent POM for org.apache.servicemix:servicemix-pom:5: Could not transfer artifact org.apache:apache:pom:7 from/to java.net (http://download.java.net/maven/2): java.net.ConnectException @ org.apache.servicemix:servicemix-pom:5, Any ideas ? If you go to the Maven repo at http://download.java.net/maven/2, you will see that no servicemix-pom artifact exists, thus the could not transfer artifact error makes sense. You need to ask the ServiceMix people about this error. This is not a Maven problem. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Incorrect assembly created with Maven 3.0.3
Thorsten Heit wrote: ...snip ... But what puzzles me is that the archives created by Maven 2.2.1 and Maven 3.0.3 are different, and I don't see a reason why... ...snip... Hi there, Did you ever get anywhere with this? I'm seeing the same problem: Maven 3.0.3 adds batik-js-1.7.jar and omits serializer-2.7.1.jar. Though I am not positive, I believe this is the cause of an exception I see at runtime, the stack trace of which starts like this: java.lang.IllegalAccessError: org/apache/xml/serializer/ExtendedContentHandler at org.apache.xalan.transformer.TransformerImpl.createSerializationHandler(TransformerImpl.java:1233) ... Thanks! -- View this message in context: http://maven.40175.n5.nabble.com/Incorrect-assembly-created-with-Maven-3-0-3-tp4393328p4811951.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
