On Tue, Sep 1, 2009 at 7:44 PM, Adam Murdoch <[email protected]> wrote:

> I've changed the script compilation to cache all scripts under
> ~/.gradle/scriptCache. An advantage of this is we no longer end up with
> .gradle directories scattered all through the source tree (unless you end up
> using an internal repository). The downside is we will need some way to
> garbage collect this cache. This isn't actually a new problem, because we
> needed to solve this any way - It's just more important now.
>
>
I like have a single place for the cache (although I was thinking about
putting the cache is the root project directory).  I wonder if Gradle might
not want to always have a "clean" task (even if not using a plugin) that
would clean the ~/.gradle stuff that is used for the current project.  The
Java plugin could then make it's "clean" task depend on this default task
(or maybe not... I know we've talked about having clean delete the script
caches because they can get out of sync and cause problems, but maybe that's
just a bug that needs to get fixed).  I don't really like Gradle always
defining a task, but this seems more like a task than a command line option.


-- 
John Murph
Automated Logic Research Team

Reply via email to