Even when I set the heap to -Xmx1024m there is still a -Xmx256m in the Grails command line, and I'm running out of memory. I can't see where this gets set. I'm running the Idea 7.0 (build 7361 I think) and JetGroovy 0.1.11732. The command line I get is:
"C:\Program Files\Java\jdk1.6.0\bin\java" -classic -Xmx1024m -ea -Xmx256M -Dgrails.home=C:\java\grails -Dbase.dir=C:\work\software\java\grails "-Dtools.jar=C:\Program Files\JetBrains\IntelliJ IDEA 7.0\jre\lib\tools.jar" -Dgroovy.starter.conf=C:\java\grails/conf/groovy-starter.conf -Xdebug -Xrunjdwp:transport=dt_socket,address=127.0.0.1:1900,suspend=y,server=n -Dfile.encoding=windows-1252 -classpath "C:\java\grails\lib\groovy-all-1.1-rc-1.jar;C:\Program Files\JetBrains\IntelliJ IDEA 7.0\lib\idea_rt.jar" org.codehaus.groovy.tools.GroovyStarter --main org.codehaus.groovy.grails.cli.GrailsScriptRunner --conf C:\java\grails/conf/groovy-starter.conf --classpath C:\java\grails\lib\groovy-all-1.1-rc-1.jar;. run-app
I don't want the -classic or the -Xmx256M
So, it will be possible to change heap size in Grails Run configuration in next JetGroovy build.
Could you say, what other parameters do you like to be customizable in run configuration? E.g. Grails/ home path, project base directory etc...
I suggest making it work like the startGrails scripts in the Grails distribution. On Linux, "-server -Xmx256M" is prepended to JAVA_OPTS to provide fallback defaults. On Windows, it appears that JAVA_OPTS is set to "-Xmx128M" if not already set, though I would guess that the Linux defaults would work as well. The VM options in the run config could be treated like JAVA_OPTS in the Grails scripts. The various path definitions (base.dir, etc) are already set from the plugin and module information, which I think should remain as-is. I don't think they have any other meaningful values for a Grails project.