Hans Dockter wrote:
With the new incremental functionality our users will have now a lot
of output like:
test UP-TO-DATE
I think it would be cool to have no output for this at all (as a
default). Usually your only interested in what needs to be done and to
see what is work in progress.
Sounds reasonable. We'd have to try this and see how it works.
For consistency:
* We should have no output for disabled tasks.
* We should show output for any buildSrc tasks that are executed.
We should also combine this with some logging at info level which
explains why a task did no work.
Related to this are tasks that are just aggregators. It would be nice
to exclude them in the output if the tasks they aggregate don't do
anything (e.g. check, classes).
My plan is to treat an aggregator task as up-to-date if all its
dependencies are up-to-date. Then, whatever we do for up-to-date tasks
will be applied to these as well.
The third catagory are task like the Copy task (e.g.
processResources). We might be able to restructure them in a way that
we could some in advance check whether something needs to be done or
not (e.g. from input exists or not).
Copy and the archive tasks don't have the full set of input and output
files registered yet. They will soon, and they will work exactly the
same as all the other tasks.
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
