On 02/12/2011, at 2:50 PM, Adam Murdoch <[email protected]> wrote:
> 2. Use gradle-wrapper.properties, so that it lives with the declaration of
> which Gradle version to use (ie this file becomes a declaration of the
> dependencies of the build itself. Could also end up with a Java version
> constraint here too).
> 3. Some other config file.
>
> I like option 2, given that we want to use the wrapper more and more, and
> that the tooling API will be easily able to make use of this.
>
> We might also have a corresponding entry in ~/.gradle/gradle.properties, too,
> so you can do a local override.
gradle-wrapper.properties makes a lot of sense to me as the public API?
This will mean that the wrapper will have to become aware whether the daemon is
going to be used or not though. If the user specifies that they want a large
minimum heap size we don't want to launch the daemon client with such a
configuration. Not a big problem though.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
