Adam Murdoch wrote:
Russel Winder wrote:
Thi relates to Trunk as at 2009-04-19 07:00:00+01:00.
I wonder if there is a way of making the output from "gradle -t" a
little less "messy". I find the output difficult to read quickly and
quick reading is what this should offer. I wonder if the problem is
having the dependencies on a line following the entry indented, e.g.:
:processTestResources - Process and copy the test resources into the
binary directory of the compiled test sources.
-> :compile
I wonder if this might work better as:
:processTestResources [ :compile ] -- Process and copy the test
resources into the binary directory of the compiled test sources.
i.e if there are dependencies then use a list in brackets following the
task name, if there are no dependencies then print nothing, not even the
brackets.
I think we might be trying to squeeze too much stuff onto 1 line.
An option is to split the report into 2 sections, where one section
lists the tasks and their dependencies (or perhaps even better, the DAG
for the task), and one section lists the tasks and their description.
Or split it into 2 reports. One would be a 'how do I use this build?'
report which lists the tasks with their descriptions, default tasks,
project descriptions. The other would be a task dependency graph report,
similar to the artifact dependency graph report.
I like this second idea. I either want to know the available tasks or the
dependencies.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
