Gradle Concepts: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
No edit summary
Line 16: Line 16:
=<span id='Build'></span>Build Lifecycle=
=<span id='Build'></span>Build Lifecycle=


A build is a Gradle execution. Each build instantiates at least one [[Gradle Project#Overview|project]], which in turn contains [[Gradle Task#Overview|tasks]], and it can be configured and controlled with [[Gradle Properties#Overview|properties]].
A build is a Gradle execution. Each build instantiates at least one [[Gradle Project#Overview|project]], which in turn contains [[Gradle Task#Overview|tasks]], and it can be configured and controlled with [[Gradle Runtime and Project Configuration#Overview|properties]].


<span id='Build_Initialization_Phase'></span>'''Initialization phase'''
<span id='Build_Initialization_Phase'></span>'''Initialization phase'''

Revision as of 02:08, 5 October 2020

External

Internal

Overview

Gradle is a general-purpose build tool. It is primarily used to build Java and Groovy, but it can build other languages as well. 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

Subjects

TO DEPLETE

Gradle Concepts TO DEPLETE