Gradle Concepts: Difference between revisions
Jump to navigation
Jump to search
Line 38: | Line 38: | ||
* <span id='Extending_Gradle'></span>[[Extending Gradle|Extending Gradle]] | * <span id='Extending_Gradle'></span>[[Extending Gradle|Extending Gradle]] | ||
* [[Gradle File Resolution]] | * [[Gradle File Resolution]] | ||
=TO DEPLETE= | |||
{{Internal|Gradle Concepts TO DEPLETE|Gradle Concepts TO DEPLETE}} |
Revision as of 22:20, 4 October 2020
External
- DSL reference https://docs.gradle.org/current/dsl/
Internal
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.
Convention over Configuration
API Documentation
DSL Documentation
Subjects
- Project
- Task, Extending Gradle with a Custom Enhanced Task
- Properties
- Gradle Instance, Settings Instance
- Logging
- Plugins
- Extending Gradle
- Gradle File Resolution