Gradle Task

External

• Task API: org.gradle.api.Task
• Task DSL: https://docs.gradle.org/current/dsl/org.gradle.api.Task.html

Internal

• Gradle Concepts

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. The goal of a Gradle execution, also known as a Gradle build, is to execute a set of tasks, in sequence.

A tasks belongs to a project. Each project comes with a set of pre-defined, built-in tasks. Each declared plugin may add its own tasks. New simple tasks can be defined in-line in build.gradle or in script plugins. Tasks whose implementations are available on the build's classpath can be declared and configured in build.gradle, as enhanced tasks, and thus made available for use during the build. Complex tasks can even be fully defined in-line or in script plugins, by providing the task code in-line in the script, though this is not a recommended practice, as it does not encourage modularization, encapsulation and sharing.

Any task instance implements org.gradle.api.Task interface. Most tasks extend directly or indirectly org.gradle.api.DefaultTask.

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.

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.

Custom Tasks

Extending Gradle with Custom Tasks

Built-in Tasks

Each build exposes a set of built-in tasks, that can be used right away without any additional configuration or loading any plugin:

• init
• wrapper
• buildEnvironment
• components
• dependencies
• dependencyInsight
• dependentComponents
• help
• model
• projects
• properties
• tasks

TO DEPLETE

Gradle Task TODEPLETE