Gradle Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
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|build lifecycle]], during which Gradle instantiates a complex domain model of the project in memory: a [[#Gralde|Gradle instance]], a [[#Settings|Settings instance]] and the [[#Project|project]] itself. | 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|build lifecycle]], during which Gradle instantiates a complex domain model of the project in memory: a [[#Gralde|Gradle instance]], a [[#Settings|Settings instance]] and the [[#Project|project]] itself. | ||
=Build Lifecycle= | =Build Lifecycle= | ||
Revision as of 21:03, 3 October 2020
External
- DSL reference https://docs.gradle.org/current/dsl/
Internal
TO DEPLETE
TO PLACE
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
Convention over Configuration
Gradle API
Gradle DSL
Gradle
Settings
Project
Task
Plugin
Properties
Extension
A plugin is the typical use case for an extension.