On Thu, Sep 24, 2009 at 4:47 PM, Hans Dockter <[email protected]> wrote:
> Hi, > > I have implemented a task optimization functionality that we might put into > 0.8. I have uploaded my branch to: > http://github.com/hansd/gradle/tree/optim > > A couple of comments: > > 1.) The task history is now stored in gradle user home with some hash that > relates it to the actual project. The base for the hash is the path of the > root dir. We might have issues if a subproject takes part in multiple > multi-project builds, if the output is sensitive to the respective > multi-project build. The only way I see to solve such a problem, would be to > have multiple output dirs. > > We have an even worse case than that: the same multi-project build is used to produce many different outputs (based on some flag). Think about a project that gets built with some subtle and some not-so-subtle changes for different customers. That's what we are doing. We handle this (in part) by redirecting the build output to a different directory for each case. This means that storing the user home will not work well for us. Maybe storing it in the project's build directory would be better? However, it's not build output but state, which is what the .gradle directories used to be for. But I'm really happy with those having been removed from my subproject directories! I'm not sure what to do here. I'll want to think about it and maybe try it out tomorrow before commenting further. -- John Murph Automated Logic Research Team
