Hello All,
The tasks report (gradle -t) at the moment presents all tasks. In a
complex build there can be plenty of them but usually only few are
really important (or to put it differently only few of them are run
from the command line, the rest is used internally but rarely called
by hand).
Right now if I have tasks like mainA, mainB, mainC (the important
ones) and AInternal, .., ZInternal (the not-so-important ones) the
report will be like this:
AInternal
BInternal
... (plenty of tasks here)
mainA
mainB
mainC
... (plenty of tasks here)
ZInternal
For many tasks, with descriptions and dependencies this makes it hard
to see what is really important.
Is there any way to make this more readable now? Any configuration
options that could be used?
What I would like to have is in general to be able to configure the
report so I could do one of the following:
A) have gradle -t show only important tasks, and gradle -tAll show all
of them (or sth similar)
B) have gradle -t show important ones first in alphabetical order and
then the rest of the tasks (also alphabetically), like this:
mainA
mainB
mainC
AInternal
BInternal
... (plenty of tasks here)
ZInternal
What do you think ?
--
Regards / Pozdrawiam
Tomek Kaczanowski
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
