Gradle Project and Build Script: Difference between revisions
Jump to navigation
Jump to search
Line 8: | Line 8: | ||
* [[Gradle_Concepts#Build_Lifecycle_and_Gradle_Objects|Gradle Concepts]] | * [[Gradle_Concepts#Build_Lifecycle_and_Gradle_Objects|Gradle Concepts]] | ||
=Overview= | |||
=Overview= | =Overview= | ||
A Project is the main API to use to interact with Gradle. All top level statements within a "build.gradle" build script are delegated to the corresponding Project instance. | |||
=Multi-Project Builds= | |||
==Root Project== | |||
==Multi-Project Build Layout== | |||
[[Gradle_Settings_Script_and_Settings_Instance#Project_Hierarchy|Project Hierarchy]] | |||
=Internal= | =Internal= |
Revision as of 22:00, 17 May 2018
External
- https://docs.gradle.org/current/dsl/org.gradle.api.Project.html
- Build script structure https://docs.gradle.org/current/dsl/#N10060
Internal
Overview
Overview
A Project is the main API to use to interact with Gradle. All top level statements within a "build.gradle" build script are delegated to the corresponding Project instance.
Multi-Project Builds
Root Project
Multi-Project Build Layout
Internal
Overview
All top level statements within a Gradle build script are delegated to the corresponding Project instance.
Top-Level Script Blocks
allprojects{}
Applies the given configuration closure, in order, to the current project and all of its sub-projects.
subprojects{}
Applies the given configuration closure, in order, to all sub-projects of the current project.