Gradle Task Dependencies and Ordering: Difference between revisions
Jump to navigation
Jump to search
Line 20: | Line 20: | ||
} | } | ||
</syntaxhighlight> | </syntaxhighlight> | ||
<syntaxhighlight lang='groovy'> | |||
task red { | |||
... | |||
} | |||
red.dependsOn: [blue, green] | |||
</syntaxhighlight> | |||
Note that a task dependency may be another task name, the task instance itself or another objects. <font color=darkgray>TODO: https://docs.gradle.org/current/javadoc/org/gradle/api/Task.html#dependencies</font> | Note that a task dependency may be another task name, the task instance itself or another objects. <font color=darkgray>TODO: https://docs.gradle.org/current/javadoc/org/gradle/api/Task.html#dependencies</font> | ||
=Implicit Dependencies= | =Implicit Dependencies= |
Revision as of 21:46, 8 October 2020
External
Internal
Overview
May times, a task requires another task to run first, especially if the task depends on the produced output of its dependency task. A task may declared its dependencies explicitly. A task may depend on other tasks implicitly, as described in the Implicit Dependencies section.
Explicit Dependencies
The Task API used to declare explicit task dependencies is Task.dependsOn(Object... paths), which surfaces in the DSL as:
task red {
dependsOn 'blue'
...
}
task red(dependsOn: [blue, green] {
...
}
task red {
...
}
red.dependsOn: [blue, green]
Note that a task dependency may be another task name, the task instance itself or another objects. TODO: https://docs.gradle.org/current/javadoc/org/gradle/api/Task.html#dependencies