Gradle Concepts: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 19: | Line 19: | ||
A build is. | A build is. | ||
=API Documentation= | |||
{{External|https://docs.gradle.org/current/javadoc/index.html}} | |||
=DSL Documentation= | |||
{{External|https://docs.gradle.org/current/dsl/index.html}} | |||
=Subjects= | =Subjects= | ||
| Line 29: | Line 34: | ||
=Convention over Configuration= | =Convention over Configuration= | ||
=Gradle= | =Gradle= | ||
{{Internal|org.gradle.api.invocation.Gradle|Gradle}} | {{Internal|org.gradle.api.invocation.Gradle|Gradle}} | ||
Revision as of 23:01, 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
A build is.
API Documentation
DSL Documentation
Subjects
Convention over Configuration
Gradle
Settings
Properties
Extension
A plugin is the typical use case for an extension.