Just wanted to point out that solutions based on environment variables 
probably won't work in the Tooling API. Unless I'm wrong, I think 
there simply is no mechanism  available to set environment parameters 
from the tooling API.

With respect to defaults, I think it is important to have sensible defaults.
(The goal should be set to defaults so that most users won't need to worry about
setting these params, and things will just be working well 'out of the box').

But it is equally important for users, including those using Gradle
via an IDE, to be able to override those defaults if they have problems
with the default values.

Kris

----- Original Message -----
> Hi,
> 
> we now have basic support for setting JVM options for the daemon VM.
> Initially I wanted to reuse the GRADLE_OPTS environment variable so
> that
> this variable would take effect for whichever VM actually runs the
> build.
> However, it's not easy/desirable to figure out from the client VM's
> startup
> script whether the build runs in daemon mode or not. Hence I've
> introduced
> another environment variable GRADLE_DAEMON_OPTS that just takes
> effect for
> the daemon VM.
> 
> What do you think about this solution? Do you have a better idea?
> 
> Another question is whether we should set a default for
> GRADLE_DAEMON_OPTS,
> in particular with regard to memory settings. Currently we don't,
> just as we
> don't set a default for GRADLE_OPTS. I'm a bit hesitant to add a
> "hidden"
> default. Maybe it's better for memory settings to be configured
> explicitly
> (or fall back to JVM defaults).
> 
> Cheers,
> Peter
> 
> 
> 
> --
> View this message in context:
> http://gradle.1045684.n5.nabble.com/Setting-JVM-options-for-daemon-VM-tp5041975p5041975.html
> Sent from the gradle-dev mailing list archive at Nabble.com.
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to