Gradle Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
<span id='Build_Initialization_Phase'></span>'''Initialization phase''' | <span id='Build_Initialization_Phase'></span>'''Initialization phase''' | ||
<span id='Build_Configuration_Phase'></span>'''Configuration phase''' | <span id='Build_Configuration_Phase'></span>'''Configuration phase'''. Tasks are [[Gradle_Task#Task_Lifecycle|instantiated and configured]]. | ||
<span id='Build_Execution_Phase'></span>'''Execution phase''' | <span id='Build_Execution_Phase'></span>'''Execution phase'''. Task actions are [[Gradle_Task#Task_Lifecycle|executed]]. | ||
=Convention over Configuration= | =Convention over Configuration= | ||
Revision as of 21:05, 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. Tasks are instantiated and configured.
Execution phase. Task actions are executed.