On 30/09/2011, at 9:38 PM, Adam Murdoch <[email protected]> wrote:
>> While trying to right some daemon tests I came unstuck because system
>> properties weren't handled the way I expected them to be. I've tracked it
>> down, and our usage of them is a bit unstructured.
>
> I'm not sure what the problem is. Can you explain it a bit more?
It's just inconsistent. I want to be able to specify the daemon idle timeout on
the command line, but it's currently read directly from GRADLE_OPTS in one spot
and System.properties on another. In both cases specifying via the command line
doesn't work.
I apologise for the previous email, it was pretty incoherent.
What I want to do is establish the rule that we read all sys props that affect
the way gradle works via the start parameter.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
