gradle

List every task the current build defines, grouped by category. `--all` shows internal / hidden tasks too.

--all; --group=<group>; --quiet

Print help text for a specific task: description, group, declared inputs / outputs.

List tasks for a specific subproject in a multi-project build (replace `<module>` with the Gradle path).

Run the standard JVM build chain: `compile → processResources → classes → jar → test → check → assemble` (and a zip distribution if configured).

-x <task> exclude task; --parallel; --build-cache; --configuration-cache

Delete the build directory (`build/`) so the next build re-runs every task from scratch.

--no-rebuild don't auto-trigger the default lifecycle

Compile and package everything but skip the verification / test tasks. Faster feedback when you only need the jar.

Run all verification tasks (`test`, `lint`, etc.) without producing a jar. Use in CI as the pre-merge gate.

--continue keep going after a task failure

Run unit tests (Test task). Use `--tests <pattern>` to narrow to specific classes / methods.

--tests com.acme.UserServiceTest; --tests '*User*'; --info

Print the resolved dependency tree for a configuration (e.g. `compileClasspath`, `runtimeClasspath`, `testCompileClasspath`).

--configuration <name>; --all show every config

Explain why a single dependency ended up at a specific version — useful for resolving version conflicts.

--dependency <group:artifact>; --configuration <name>

Print the resolved build-script classpath — every plugin / helper library the build itself uses.

Force re-resolution of dynamic versions and snapshot dependencies.

--refresh-keys

List every project in the reactor (root + subprojects) with their project paths and descriptions.

Run a task in one subproject by Gradle path (`:` separator).

-p <dir> start from a subdir

Execute independent tasks in parallel — useful for multi-module builds with independent test suites.

--max-workers=<N>; --no-parallel

Enable the local build cache (task outputs reused across branches / branches). Combine with a remote cache in `settings.gradle` for CI.

--no-build-cache

Gradle 8.x — cache the configuration phase for sub-millisecond startup of large multi-project builds.

--no-configuration-cache

Disable the Gradle daemon — useful for low-memory CI or for diagnosing daemon-only bugs.

Stop all running Gradle daemons. Pair with a clean rebuild if cached state is suspect.

Run a task then publish a build scan (link printed at end). Requires accepting the Build Scan terms once.

--scan -Dscan.tag.<name>=<value>

Enable INFO logging — task start / finish, up-to-date checks, dependency resolutions.

--debug / -d even more detail

Print full stack traces on any failure.

--warning-mode=all show every deprecation warning

Run a task through the Gradle Wrapper — uses the Gradle version pinned in `gradle/wrapper/gradle-wrapper.properties`.

Generate / refresh the wrapper files with a specific Gradle distribution.

--distribution-type bin | all; --gradle-distribution-url <url>

Upload artifacts to the repository declared under `publishing` in `build.gradle`. Common targets: Maven Central via Sonatype, private Nexus / Artifactory.

-Drelease.useAutomaticVersion=true; -PpublishTo=staging

Install the build into the local Maven repository (`~/.m2/repository`) so a neighboring Maven build can depend on it.

Print Gradle / JVM / OS info, including the daemon status.

List every project property (ext.*, gradle.*, system) — useful when chasing overridden values.

Bootstrap a new Gradle project: choose DSL (Groovy / Kotlin), pick a project type, optionally wire a Git remote.

--type basic; --type java-application; --type java-library; --dsl groovy|kotlin

Filter the task list to a single task group (e.g. `build`, `verification`, `documentation`, `help`).