Extending Gradle: Difference between revisions
Line 16: | Line 16: | ||
==Simple Task== | ==Simple Task== | ||
A simple task is defined with an in-line action closure. | A simple task is defined with an in-line action closure in the build script or another script imported from the build script. | ||
==Enhanced Task== | ==Enhanced Task== |
Revision as of 22:57, 23 September 2020
Internal
Overview
The simplest way to extend Gradle is to write a custom task, which can be declared in-line in build.gradle or can be part of a different artifact.
Custom Task
The simplest way of extending Gradle is write a custom task. The custom task can be declared in-line in the default build script build.gradle, as a simple task. The simple task can also be declared in-line in a separate build script, which is then included from the default build script. The code of the custom task can live in a separate source file, which in turn can be declared in a special area of the Gradle project, or can be share with other projects as part of a library. Such a task is referred to as a standalone custom task.
Task. DEPLETE Gradle_Task_TODEPLETE#Explicit_Task_Declaration_.28Custom_Tasks.29
Simple Task
A simple task is defined with an in-line action closure in the build script or another script imported from the build script.
Enhanced Task
Standalone Custom Task
Using the Custom Task
Enhanced task.
Simple Task
Enhanced Task