On 30/07/10 7:31 PM, Hamlet D'Arcy wrote:
I would love to see more control over the -t output.
In Ant, it is quite easy to control the ant -p output... if the target
has a description then it appears in this list, if not then it won't.
Using this simple rule it was easy to create self documenting Ant
builds.
This is pretty much how -t will work by default: If a task has a task
group, then it is shown in the output, otherwise it won't. There will
also be some way to ask for more detail, similar to what -t shows now.
We're not quite at this point in trunk, but we should have this for 0.9.
There are a few other places in Gradle where this information might be
useful. One is the GUI/IDE plugin, which could present these 'lifecycle'
tasks differently to the 'implementation' tasks (possibly rendering them
differently, or a hide/show toggle, or displaying them in a tree, or
whatever). Another place is in Gradle's console output. For example, we
might not display the 'someTask UP-TO-DATE' message for implementation
tasks, and instead collapse them into the message for the lifecycle tasks.
Another approach we want to take to reducing the noise of -t is to get
better at not adding tasks which are not required for a given build. For
example, if the jar isn't required, the java plugin shouldn't add it.
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
CTO, Gradle Inc. - Gradle Training, Support, Consulting
http://www.gradle.biz
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
