A similar problem occurs if you have a custom task in buildSrc, changing it doesn't force a full rebuild even though it might cause changes. I would guess it would be hard to do much more than "if change full rebuild" as tracking what groovy code depends on other groovy code would be really hard.
Philip On Tue, Jul 19, 2011 at 10:53 AM, 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 > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
