search

pombreda / gwt-maven

Automatically exported from code.google.com/p/gwt-maven
0 stars 1 forks source link

Option to specify the jvm (or path to the java executable) #184

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Is it possible to add another field to maven-googlewebtoolkit2-plugin
configuration? Now you got extraJvmArgs there, but I'm missing the
possibility to set jvm as well. And then use this value in the gwtTest
scripts that are generated? There's some well known issues with gwt and
java 64bit. In an automatic build environment this setting would solve a lot!

Original issue reported on code.google.com by knut.johannes.dahle@gmail.com on 11 Dec 2008 at 4:28

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I've made a patch for this functionality. Hope you will include it in the next 
release.

Original comment by knut.johannes.dahle@gmail.com on 16 Dec 2008 at 9:08

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by charlie....@gmail.com on 4 Jan 2009 at 4:23

GoogleCodeExporter commented 9 years ago 
I will try to get the patch applied, yes.

I think the general workaround for this though, is just to start Maven itself 
with
whichever JVM you want used - as that is the one GWT-Maven will pick up.

Original comment by charlie....@gmail.com on 24 Jan 2009 at 11:22

GoogleCodeExporter commented 9 years ago

Original comment by charlie....@gmail.com on 26 Jan 2009 at 11:02

GoogleCodeExporter commented 9 years ago 
patch applied rev 966

Original comment by keber...@gmail.com on 22 Mar 2009 at 9:09

GoogleCodeExporter commented 9 years ago 
In 2.0-RC1.

Original comment by charlie....@gmail.com on 3 Apr 2009 at 1:16