Gradle Operations TODEPLETE

DEPLETE TO

Gradle Operations

Operations

Start a Project

gradle init

Creates a project structure that includes:

• build.gradle
• settings.gradle
• a project-level gradle directory
• a project-level .gradle directory
• gradlew, gradlew.bat

Note that in some cases, the execution flag is not set on gradlew, so you may have to set it manually.

Gradle Project Initialization Script

This is a script that is a little bit more complex than gradle init. The script creates the project root directory, interactively queries project elements, such as the initial package name, etc. It then will will create the initial package and a simple Main class, will initialize build.gradle with the minimal configuration required to build a Java project and it will put in place the run wrapper.

GitHub Playground gradle-init

List Sub-Projects

gradle projects

Inspect Dependencies, Generate Dependency Tree

https://docs.gradle.org/current/userguide/inspecting_dependencies.html

The full graph of the project's dependencies can be rendered. The selection reason and origin for a dependency can also be displayed.

To display the dependency trees for all dependency configurations of the project, execute:

gradle -q dependencies

The result is called a dependency report. Any dependency that could not be resolved is marked with FAILED in red color. Dependencies with the same coordinates that can occur multiple times in the graph are omitted and indicated by an asterisk. Dependencies that had to undergo conflict resolution render the requested and selected version separated by a right arrow character. The dependency report provides the raw list of dependencies but does not explain why they have been selected or which dependency is responsible for pulling them into the graph. These explanations can though be generated, see Identify Why a Specific Dependency was Selected.

To display the dependency tree for just one dependency configuration:

gradle -q dependencies --configuration <configuration-name>

Identify Why a Specific Dependency was Selected

gradle -q dependencyInsight --dependency <dependency-name> [--configuration <configuration-name>]

Print the Runtime Classpath

task printClasspath {
        doLast {
            configurations.runtimeClasspath.each { print it; print ':' }
        }
}

Then Gradle must be run with "-q" option to discard extraneous output:

gradle -q printClasspath

Run a Specific Test

gradle test --tests "com.example.MyTests.mySingleTest"

Do Not Use Gradle Daemon to Run the Build

gradle --no-daemon ...

Useful when debugging Gradle configuration scripts.

Pass Configuration on Command Line

Gradle Pass Configuration on Command Line

Pass Configuration via Custom Environment Variables

Pass Configuration via Custom Environment Variables

Artifact Publishing Operations

Artifact Publishing Operations

Command-Line Interface

https://docs.gradle.org/current/userguide/command_line_interface.html

Tasks

build

gradle build 

Build a sub-project:

gradle :<sub-project-name>:build

Build without Tests

Build without tests. Works with simple projects or multi-project builds.

gradle build -x test
gradle build -x :some-project:test

projects

gradle projects

tasks

Displaying Tasks

properties

Displays project properties, properties added by various plugins and their default values.

gradle properties