Gradle Task: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 24: Line 24:


Any build comes with a number of pre-defined default tasks, regardless on whether plugins have been applied or not.
Any build comes with a number of pre-defined default tasks, regardless on whether plugins have been applied or not.
gradle dependencies
Displays all dependencies declared in project ':subproject-A'.
gradle dependencyInsight
Displays the insight into a specific dependency in project ':subproject-A'.
gradle dependentComponents
Displays the dependent components of components in project ':subproject-A'.
gradle model
Displays the configuration model of project ':subproject-A'. [incubating]
gradle projects
Displays the sub-projects of project ':subproject-A'.
gradle properties
Displays the properties of project ':subproject-A'.
gradle tasks
Displays the tasks runnable from project ':subproject-A'.
gradle buildEnvironment
Displays all buildscript dependencies declared in project ':subproject-A'.
gradle components
Displays the components produced by project ':subproject-A'.


==Tasks From Plugins==
==Tasks From Plugins==

Revision as of 23:09, 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. Gradle builds the complete dependency graph before any tasks is executed.

All tasks known to a build can be displayed with:

gradle tasks

The tasks known to a specific project can be displayed with:

gradle :<project-path>:tasks

Task Sources

Default Tasks

Any build comes with a number of pre-defined default tasks, regardless on whether plugins have been applied or not.

gradle dependencies

Displays all dependencies declared in project ':subproject-A'.

gradle dependencyInsight

Displays the insight into a specific dependency in project ':subproject-A'.

gradle dependentComponents

Displays the dependent components of components in project ':subproject-A'.

gradle model

Displays the configuration model of project ':subproject-A'. [incubating]

gradle projects

Displays the sub-projects of project ':subproject-A'.

gradle properties 

Displays the properties of project ':subproject-A'.

gradle tasks 

Displays the tasks runnable from project ':subproject-A'.

gradle buildEnvironment

Displays all buildscript dependencies declared in project ':subproject-A'.

gradle components

Displays the components produced by project ':subproject-A'.

Tasks From Plugins

Plugins that have been applied to the project may come with their own tasks. This is a non-exhaustive list:

Explicit Task Declaration

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.

Task Types

TODO: https://docs.gradle.org/current/dsl/#N10376