JVMArgs are not propagating to compc.jar
I tried using both gradle.properties, and setting GRADLE_OPTS.
My project won't build because the heap fills up.
Here you can see what I mean:
501 75695 67753 0 10:35PM ttys000 0:44.48 /usr/bin/java -Xms2048m -Xmx4096m -XX:-UseGCOverheadLimit -XX:MaxPermSize=512m -XX:ReservedCodeCacheSize=256m -Xdock:name=Gradle -Xdock:icon=/Users/ash/Runtimes/gradle-1.6/media/gradle.icns -Dorg.gradle.appname=gradle -classpath /Users/ash/Runtimes/gradle-1.6/lib/gradle-launcher-1.6.jar org.gradle.launcher.GradleMain build
501 75767 75695 0 10:35PM ttys000 0:32.82 /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java -jar /Users/ash/.gradle/gradleFx/sdks/b00e71b2106bafeef8c86b6340c39ecc0fc36f8c/lib/compc.jar -runtime-shared-library-path=
The gradle-launcher, get's the memory settings as expected, but the compc.jar task does not.
Is there any easy workaround available? - I'm desperately trying to move away from flexmojos.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Yennick Trevels on 16 Aug, 2013 08:57 PM
Hi!
You can set jvm arguments for the compc task (or any other compile task) with the jvmArguments property, like this:
2 Posted by dylancjaneke on 16 Aug, 2013 09:01 PM
ah, ok - thank you - that was a very quick response, is there any way that it could be inherited from gradle.properties?
3 Posted by dylancjaneke on 16 Aug, 2013 09:07 PM
Nevermind me! I got it:
jvmArguments = project.ext['org.gradle.jvmargs'].tokenize().asList()
Good riddance Maven! Thanks for the help, I'm really liking GradleFX.
dylancjaneke closed this discussion on 16 Aug, 2013 09:07 PM.