On 17/06/10 3:04 PM, vincer wrote:
That would be nice. My company has an automated build system and there's a
policy that no files are to be created in the project directory at build
time.
While reading about this I found this in section 12.7 of the docs:
"If you run Gradle with the -C off option, any existing cache is ignored and
the build script is compiled and executed on the fly"
But this option doesn't work in real life and there's no mention of it in
the command line help text. Is this an option that is in the works as well
or was removed?
This option (-C off) was removed. I've updated the docs to remove this
mention of it.
Adam Murdoch-3 wrote:
On 17/06/10 10:42 AM, vincer wrote:
Is there a way to specify where the .gradle directory that holds the
cache.bin and other project specific files goes?
There's no way to change this. It's always in $projectDir/.gradle.
One option we've talked about is to move the contents of
$projectDir/.gradle to $userDir/.gradle, which does have a command-line
option to specify where it goes.
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
CTO, Gradle Inc. - Gradle Training, Support, Consulting
http://www.gradle.biz
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
CTO, Gradle Inc. - Gradle Training, Support, Consulting
http://www.gradle.biz
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
