Gradle Project: Difference between revisions
No edit summary |
|||
Line 36: | Line 36: | ||
} | } | ||
</syntaxhighlight>More details in: {{Internal|Gradle Dependencies and Configurations|Gradle Dependencies and Configurations}} | </syntaxhighlight>More details in: {{Internal|Gradle Dependencies and Configurations|Gradle Dependencies and Configurations}} | ||
=Project Coordinates= | |||
{{Internal|Gradle Project Coordinates|Gradle Project Coordinates}} | |||
=Project Directory= | =Project Directory= |
Revision as of 00:52, 4 October 2020
External
- Project API: org.gradle.api.Project
- Project DSL: https://docs.gradle.org/current/dsl/org.gradle.api.Project.html
Internal
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 and configurations can be managed with the "dependencies" and "configurations" DSL elements:
dependencies {
// configuration closure
}
configurations {
// configuration closure
}
More details in: