Gradle Task: Difference between revisions
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
=Task Structure= | =Task Structure= | ||
==Task Name== | ==Task Name== | ||
Each task has a name, which is unique within the context of its owning project. | Each task has a name, which is unique within the context of its owning project. The name must not contain dashes. | ||
==Task Path== | ==Task Path== | ||
A task path is the concatenation of the task owning project name and the task name, separated by the ":" character. | A task path is the concatenation of the task owning project name and the task name, separated by the ":" character. | ||
Revision as of 22:31, 3 October 2020
External
Internal
Overview
A task represents a well defined piece of work that is executing during a build, such as compiling Java classes or creating a distribution file.
A tasks belongs to a project.
Task Structure
Task Name
Each task has a name, which is unique within the context of its owning project. The name must not contain dashes.
Task Path
A task path is the concatenation of the task owning project name and the task name, separated by the ":" character.
Declaring a Task
With DSL
Programmatically
Task API
Overview
With no plugins, a build has a small set of built-in tasks.
Each plugin typically adds more.
Custom tasks can be added in build.gradle or script plugins.
Task Configuration Closure
Task Action
Task Action Closure
Task action closures can be used to define custom simple tasks, in-line in build.gradle or in a script plugin.