Gradle Project: Difference between revisions
| Line 34: | Line 34: | ||
// configuration closure | // configuration closure | ||
} | } | ||
</syntaxhighlight>More details in {{Internal|Gradle Dependencies|Gradle Dependencies}} | </syntaxhighlight>More details in: {{Internal|Gradle Dependencies|Gradle Dependencies}} | ||
=Project Directory= | =Project Directory= | ||
=Multi-Project Builds= | =Multi-Project Builds= | ||
{{Internal|Gradle Multi-Project Builds#Overview|Multi-Project Builds}} | {{Internal|Gradle Multi-Project Builds#Overview|Multi-Project Builds}} | ||
Revision as of 00:41, 4 October 2020
External
- Project API: org.gradle.api.Project
- Project DSL: https://docs.gradle.org/current/dsl/org.gradle.api.Project.html
Internal
TO DEPLETE
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. The project instance is not available in settings.gradle, only the root project descriptor via rootProject variable, which corresponds to Settings.getRootProject().
Project API and build.gradle DSL
The build script classpath for the project can be configured with Project.buildscript(Closure) which corresponds to the "buildscript" DSL element:
buildscript {
// configuration closure
}
More details are available in:
Plugins for the build can be declare with PluginAware.apply(...), which corresponds to the "apply" DSL element:
apply plugin:|from: '...'
More details on using plugins are available in:
Dependencies can be managed with Project.dependencies(Closure), Project.getDependencies() and the "dependencies" DSL element:
dependencies {
// configuration closure
}
More details in: