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.