Gradle Concepts: Difference between revisions
Jump to navigation
Jump to search
(→Plugin) |
|||
| Line 38: | Line 38: | ||
{{Internal|Gradle Plugin Concepts|Gradle Plugin Concepts}} | {{Internal|Gradle Plugin Concepts|Gradle Plugin Concepts}} | ||
{{Internal|Extending Gradle|Extending Gradle}} | {{Internal|Extending Gradle|Extending Gradle}} | ||
=Properties= | |||
{{Internal|Gradle Properties|Properties}} | |||
=Extension= | =Extension= | ||
A [[Gradle_Plugin_Concepts#Plugin_Extension|plugin]] is the typical use case for an extension. | A [[Gradle_Plugin_Concepts#Plugin_Extension|plugin]] is the typical use case for an extension. | ||
Revision as of 20:20, 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 evolves 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.