Gradle Properties - Runtime and Project Configuration: Difference between revisions
Line 6: | Line 6: | ||
"Properties" in this context represent external configuration elements passed to a [[Gradle_Concepts#Build_Lifecycle|Gradle build]] to modify the behavior of the Gradle runtime itself, or the behavior of tasks being executed by various projects that are part of the build. Gradle supports many kinds of "properties". Configuration can be passed as command line flags, system properties, Gradle properties, environment variables and project properties. All these configuration elements are provided externally and injected into the build. It is also possible to define properties in the build scripts and pass configuration around between different elements of the build. Those properties are named "extra properties". Since build scripts may include executable code, it is also possible to use local variables, which are a feature of the underlying Groovy language. | "Properties" in this context represent external configuration elements passed to a [[Gradle_Concepts#Build_Lifecycle|Gradle build]] to modify the behavior of the Gradle runtime itself, or the behavior of tasks being executed by various projects that are part of the build. Gradle supports many kinds of "properties". Configuration can be passed as command line flags, system properties, Gradle properties, environment variables and project properties. All these configuration elements are provided externally and injected into the build. It is also possible to define properties in the build scripts and pass configuration around between different elements of the build. Those properties are named "extra properties". Since build scripts may include executable code, it is also possible to use local variables, which are a feature of the underlying Groovy language. | ||
All these configuration and component state elements are readable from the build scripts. | |||
Revision as of 02:14, 5 October 2020
External
Internal
Overview
"Properties" in this context represent external configuration elements passed to a Gradle build to modify the behavior of the Gradle runtime itself, or the behavior of tasks being executed by various projects that are part of the build. Gradle supports many kinds of "properties". Configuration can be passed as command line flags, system properties, Gradle properties, environment variables and project properties. All these configuration elements are provided externally and injected into the build. It is also possible to define properties in the build scripts and pass configuration around between different elements of the build. Those properties are named "extra properties". Since build scripts may include executable code, it is also possible to use local variables, which are a feature of the underlying Groovy language.
All these configuration and component state elements are readable from the build scripts.
Properties are exposed by projects and tasks and help to configure and control the build.
Gradle Project Coordinates and State Properties