Hi Ken,
On Thu, Aug 16, 2012 at 3:19 PM, Ken Sipe wrote:
> I would recommend what the git guys do with git config.
>
> You still want to debate the default... But there should be configs for a
> project and for a system (global). Perhaps the gradle file already provides
> the project level...
>
Hans > The other part of the story is to provide a way on the command line to
switch the daemon on or off without touching any property files yourself (e.g.
gradle --daemon)
Our preference is not for users to edit the files, it's just that we haven't
added the UI to avoid this _yet_.
On 16/08/
I would recommend what the git guys do with git config.
You still want to debate the default... But there should be configs for a
project and for a system (global). Perhaps the gradle file already provides the
project level...
While command-line execution config makes sense to me... It may no
On 16/08/2012, at 9:15 AM, Hans Dockter wrote:
> We made the decision in the past that for now we don't want to switch on the
> daemon by default. This is mostly because we don't recommend using the daemon
> on CI boxes and people shouldn't run into issues there because they are not
> aware to
We made the decision in the past that for now we don't want to switch on
the daemon by default. This is mostly because we don't recommend using the
daemon on CI boxes and people shouldn't run into issues there because they
are not aware to switch the daemon off on those machines.
But on dev machin
