Gradle Command Line

Internal

• Gradle Operations
• Gradle Properties - Runtime and Project Configuration

Overview

In case of a multi-project, Gradle command can be executed from the root of the project or from any sub-projects.

Some command line options have the same effect as setting corresponding properties or environment variables. When a command line option is present, it has precedence over the equivalent properties or environment variables. More details in:

Gradle Variables and Properties

Command Line Flags

--help

In-line help.

--version

./gradlew --version

gradle --version

--q,--quiet

Only warning and error category output is displayed. The logger "quiet" category can be accessed with:

logger.quiet "will be displayed even in quiet mode"

Also see:

Gradle Logging

-m,--dry-run

Run the builds with all task actions disabled.

-i,--info

When executed with -i, Gradle displays the tasks that are executed, in the order in which they are executed. Additionally, -m|--dry-run can be used to simulate the execution without actually performing the task actions.

Also see:

Gradle Logging

-d,--debug

Also see:

Gradle Logging

-P<property-name>=<property-value> Project Properties

See:

Gradle Project Coordinates, State and Configured Properties

-D<property-name>=<property-value> System Properties

See:

Gradle System Properties

-x,--exclude-task

https://docs.gradle.org/current/userguide/command_line_interface.html#sec:excluding_tasks_from_the_command_line

Execute without the task following -x. For example, if I want to execute a build without tests:

gradle build -x test

or if I want to publish without running the javadoc task:

gradle build publish -x javadoc

--continue

Also see Ordering Tasks.

--no-daemon

See:

Gradle Daemon

--stop

See:

Gradle Daemon Operations | Stop

--status

See:

Gradle Daemon Operations | Status

--refresh-dependencies

Gradle Dependencies and Dependency Configurations | Forced Cache Update

Built-in Tasks

• gradle tasks
• gradle wrapper
• gradle init