On 12/08/10 9:28 PM, Tomek Kaczanowski wrote:
Hello Chris,
It's because you have not assigned those tasks a 'group'.
:) Yes I know that I haven't assigned them to any group. The question
should have rather been: "why from 50 tasks I have in my build.gradle
only these 3 were selected to 'other tasks' group?".
And my guess it, that is because no other tasks depend on them. Right ?
That's exactly right. The idea is that gradle -t by default shows only
the 'main tasks' of a project, where a 'main task' is one which a (new)
user is most likely interested in running. At the moment a main task is
defined as a task which is assigned to a group or a task which no other
task depends on.
This is a bit of an experiment, so feedback is welcome. I didn't want to
just list the tasks which are assigned to a group for a couple of reasons:
- I wanted every task to be reachable in some form via those listed by
gradle -t.
- I wanted include custom tasks in some way, to make it apparent that
the output is dynamic and driven by the actual task graph, rather than
just some static text.
The problems with this approach, I think, are that some actual main
tasks will be missed from the 'other tasks' group, and also that having
this group at all is going to cause some confusion as to why those
particular tasks are there and not others.
--
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
