Gradle Project: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 13: Line 13:
A Gradle project typically represents a software component to be built by executing a set of [[Gradle Task#Overview|tasks]] in sequence. A project has a direct class representation in the Gradle domain model: [https://docs.gradle.org/current/javadoc/org/gradle/api/Project.html org.gradle.api.Project].
A Gradle project typically represents a software component to be built by executing a set of [[Gradle Task#Overview|tasks]] in sequence. A project has a direct class representation in the Gradle domain model: [https://docs.gradle.org/current/javadoc/org/gradle/api/Project.html org.gradle.api.Project].


The project instance is available to the [[build.gradle]] script via the "project" variable, but not to [[settings.gradle]], because at the stage in the build lifecycle when [[settings.gradle]]
The project instance is available to the [[build.gradle]] script via the "project" variable, which corresponds to the [https://docs.gradle.org/current/javadoc/org/gradle/api/Project.html#getProject-- Project.getProject()] accessor.


=Project Directory=
=Project Directory=

Revision as of 23:51, 3 October 2020

External

Internal

TO DEPLETE

Gradle Project and Build Script

Overview

A Gradle project typically represents a software component to be built by executing a set of tasks in sequence. A project has a direct class representation in the Gradle domain model: org.gradle.api.Project.

The project instance is available to the build.gradle script via the "project" variable, which corresponds to the Project.getProject() accessor.

Project Directory