Settings.gradle: Difference between revisions
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
* [[Gradle_Concepts#Configuration_Scripts_and_Core_Types|Gradle Concepts]] | * [[Gradle_Concepts#Configuration_Scripts_and_Core_Types|Gradle Concepts]] | ||
=Overview= | =Overview= | ||
The settings file defines which projects are taking part in a multi-project build, and it is optional for a single-project build. It can also be used to add libraries to the build scripts classpath. The default name is <tt>settings.gradle</tt>. The settings file is referred to as an Gradle settings script. The file is executed during the [[Gradle_Concepts#Initialization_Phase|initialization phase]]. | The settings file defines which projects are taking part in a multi-project build, and it is optional for a single-project build. It can also be used to add libraries to the build scripts classpath. The default name is <tt>settings.gradle</tt>. The settings file is referred to as an Gradle settings script. The file is executed during the [[Gradle_Concepts#Initialization_Phase|initialization phase]]. During execution, property access and method calls are delegated to the Settings instance. | ||
=How Gradle Looks for a Settings File= | =How Gradle Looks for a Settings File= | ||
Revision as of 00:45, 22 October 2020
External
Internal
Overview
The settings file defines which projects are taking part in a multi-project build, and it is optional for a single-project build. It can also be used to add libraries to the build scripts classpath. The default name is settings.gradle. The settings file is referred to as an Gradle settings script. The file is executed during the initialization phase. During execution, property access and method calls are delegated to the Settings instance.