Gradle Task: Difference between revisions
| Line 9: | Line 9: | ||
=Overview= | =Overview= | ||
A ''task'' is a core Gradle concept. It represents a single atomic piece of work for a build, such as compiling classes or generating javadoc. A build consists in executing a sequence of tasks in succession. Tasks may be explicitly declared in [[build.gradle]] using Project's task() method. As an example, of the simplest possible task declarations is: | A ''task'' is a core Gradle concept. It represents a single atomic piece of work for a build, such as compiling classes or generating javadoc. A build consists in executing a sequence of tasks in succession. Gradle computes the [[Directed Acyclic Graph]] of to be executed in order to fulfill the tasks specified on command line, and then executes them honoring inter-task dependencies and insuring the fact that a task is executed only once. | ||
Tasks may be explicitly declared in [[build.gradle]] using Project's task() method. As an example, of the simplest possible task declarations is: | |||
<syntaxhighlight lang='groovy'> | <syntaxhighlight lang='groovy'> | ||
Revision as of 22:57, 17 May 2018
External
Internal
Overview
A task is a core Gradle concept. It represents a single atomic piece of work for a build, such as compiling classes or generating javadoc. A build consists in executing a sequence of tasks in succession. Gradle computes the Directed Acyclic Graph of to be executed in order to fulfill the tasks specified on command line, and then executes them honoring inter-task dependencies and insuring the fact that a task is executed only once.
Tasks may be explicitly declared in build.gradle using Project's task() method. As an example, of the simplest possible task declarations is:
task sample {
println 'this is a simple task'
}
A task declared as above will be executed during the configuration phase, not execution. Investigate, this seems odd.
Plugins that have been applied to the project may come with their own tasks.