[GRADLE-121] Offer option to print out the DAG for executing a particular task. This should also be printed out in debug mode. Created: 17/Jun/08  Updated: 04/Jan/13  Resolved: 23/Jun/09

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 0.7

Type: Improvement
Reporter: Hans Dockter Assignee: Hans Dockter
Resolution: Duplicate Votes: 0

Issue Links:
Duplicates GRADLE-523 Offer a dry-run option for a Gradle b... Resolved


If the -t option is used right now we print out all tasks and there dependencies. We should enhance this feature If a task name is passed together with the -t option we should print out the DAG for this task. This DAG printing should also happen in the log with log level debug.

Comment by Jon Cox [ 23/Jan/09 ]


It might also be nice to have a mode where you also emit information
on the dependency configuration(s) that are linked to that task,
and the artifacts associated with that dependency configuration.

This way, you'd have a crystal clear diagnostic that shows you what
depends on what as far as execution goes coordinated with information
on what assets those executions require to succeed (and why).

Comment by Hans Dockter [ 08/Feb/09 ]

What we could do is to offer some standard way if you call it from the command line. If you need something more sophisticated, our user's can write a task and the DAG class would offer them some query and render methods

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