On 04/12/2011, at 9:07 AM, Luke Daley wrote: > > > > > 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.
Only until the daemon is switched on by default. To start with, when you run in daemon mode or use the tooling API, the setting will be honoured. But, if you run in non-daemon mode, the setting will not be honoured. Once we get rid of non-daemon mode, the setting will always be used. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
