Why not create a hash of each task once the build file has been processed, and record that alongside the hash of the input and output files?
Mike On 20 Jul 2011 00:53, "Hans Dockter" <[email protected]> wrote: > Build file changes might affect the output of a task. Yet they are not taken > into consideration for the up to date check. At one point we could try to be > really smart about them (e.g. checking the section of the change in the > build file and thus determining which tasks are not up to date). > > For now I would propose the following behaviour: > > - If the build file has changed, rebuild the cache > - Provide some way for a power user to disable rebuilding the cache. > > Hans > > -- > Hans Dockter > Founder, Gradle > http://www.gradle.org, http://twitter.com/gradleware > CEO, Gradleware - Gradle Training, Support, Consulting > http://www.gradleware.com
