[GRADLE-1067] -t task listing in a multi-project build should show the unique set of tasks across all projects Created: 28/Jul/10  Updated: 04/Jan/13  Resolved: 12/Jan/11

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 0.9-rc-2

Type: Improvement
Reporter: Chris Beams Assignee: Unassigned
Resolution: Fixed Votes: 0


Currently, a gradle -t in the root project of a multi-project build lists only the tasks defined for the root project itself.

From an ease of use and discoverability point of view, -t should take into account any subprojects and create a listing of the union of all tasks across all projects.

Without this functionality, a build user must either cd into each respective subproject and do a -t listing therein, or issue a -t?, which results in a firehose of duplicate information to sort through.

Comment by Adam Murdoch [ 28/Jul/10 ]

This could probably be implemented in such as way that we can get rid of -t ? altogether, when this fix for this issue is combined with the fix for GRADLE-1059.

Comment by Adam Murdoch [ 28/Jul/10 ]

The GUI should do this too, in the task tree.

Comment by Adam Murdoch [ 12/Jan/11 ]

This was done in 0.9-rc-2.

Generated at Wed Jun 30 11:46:03 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.