Gradle Task: Difference between revisions
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
=Task Structure= | =Task Structure= | ||
==Task Name== | |||
Each task has a name, which is unique within the context of its owning project. | |||
==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= | =Declaring a Task= | ||
Revision as of 22:30, 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.
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 Name
Define task name constraints. A dash is not allowed.
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.