Gradle Project: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
Line 7: Line 7:
* [[build.gradle]]
* [[build.gradle]]


=TO DEPLETE=
{{Internal|Gradle Project and Build Script|Gradle Project and Build Script}}
=Overview=
=Overview=


Line 42: Line 40:
=Multi-Project Builds=
=Multi-Project Builds=
{{Internal|Gradle Multi-Project Builds#Overview|Multi-Project Builds}}
{{Internal|Gradle Multi-Project Builds#Overview|Multi-Project Builds}}
=TO DEPLETE=
{{Internal|Gradle Project and Build Script|Gradle Project and Build Script}}

Revision as of 00:52, 4 October 2020

External

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:

Build Script Classpath

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:

Using a Plugin

Dependencies and configurations can be managed with the "dependencies" and "configurations" DSL elements:

dependencies {
  // configuration closure
}
configurations {
  // configuration closure
}

More details in:

Gradle Dependencies and Configurations

Project Directory

Multi-Project Builds

Multi-Project Builds

TO DEPLETE

Gradle Project and Build Script