Gradle Concepts: Difference between revisions
Jump to navigation
Jump to search
Line 39: | Line 39: | ||
* <span id='Plugin'></span><span id='Gradle_Plugin'></span>[[Gradle Plugin Concepts|Plugins]] | * <span id='Plugin'></span><span id='Gradle_Plugin'></span>[[Gradle Plugin Concepts|Plugins]] | ||
* <span id='Extending_Gradle'></span>[[Extending Gradle|Extending Gradle]] | * <span id='Extending_Gradle'></span>[[Extending Gradle|Extending Gradle]] | ||
* [[Gradle File Resolution]] |
Revision as of 03:40, 4 October 2020
External
- DSL reference https://docs.gradle.org/current/dsl/
Internal
TO DEPLETE
Overview
The goal of a Gradle execution, also known as a Gradle build, is to execute a set of tasks, in sequence. Each build runs according to a well defined build lifecycle, during which Gradle instantiates a complex domain model of the project in memory: a Gradle instance, a Settings instance and the project itself.
Build Lifecycle
A build is a Gradle execution. Each build instantiates at least one project, which in turn contains tasks, and it can be configured and controlled with properties.
Initialization phase
Configuration phase
Execution phase