Hi John, On Tue, Mar 9, 2010 at 5:42 PM, John Murph <[email protected]> wrote:
> On Mon, Mar 8, 2010 at 7:08 PM, Adam Murdoch <[email protected]> wrote: > >> >> Right now, a really simple option would be for the dependency analysis to >> delete all output classes when the classpath changes. >> >> > Doesn't that amount to a "clean build" every time something changes? > That's simple but unacceptable as it turns a 2 minute build (with the depend > call) into a 12 minute build. > Depending on the build, this is very different from a clean build. A lot of stuff in the build might not be affected by class changes (e.g. pdf doc generation). Furthermore, if a leaf subproject is changed nothing else is affected. Of course if a core project is changed on which many other subprojects depend, then a lot of things need to be retriggered. The compile is for many builds not the most expensive part in that respect. You need to retest, rejar, .... Yet even with the current behavior, the average build time will dramatically decrease for many multi-project builds. And there is more smartness to come in the future: - Parallel testing - Incremental testing - Incremental compile - Hans -- Hans Dockter Founder, Gradle http://www.gradle.ordle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz > > -- > John Murph > Automated Logic Research Team >
