On 02/12/2011, at 12:53 PM, Kris De Volder wrote: > 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.
My idea here would be that the daemon itself has no knowledge of environment parameters, but reading the environment parameters (or whatever) happens internally when creating daemon processes. What I mean is that the tooling API should be able to specify this information, allowing the tooling api client to collect this information however it wishes (e.g. preference pane in the IDE) and provide it. > 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'). Agreed. I think we should shoot for sensible defaults here instead of avoiding the complexity of having defaults. > 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. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
