Gradle Operations

Internal

• Gradle

Installation

Gradle Installation

Command Line

Gradle Command Line

Operations

Debug a Gradle Build

https://docs.gradle.org/current/userguide/troubleshooting.html#sec:troubleshooting_build_logic

External Gradle Process

Gradle Process Instrumentation

Use -Dorg.gradle.debug=true. Experimented with Gradle 6.8.3.

./gradlew -Dorg.gradle.debug=true --no-daemon <task-to-debug>

Even if --no-daemon was specified, Gradle will issue a message similar to:

To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/6.8.3/userguide/gradle_daemon.html#sec:disabling_the_daemon.
> Starting Daemon

and will stop there waiting for the debugger to attach. The JVM will listen on 5005.

If you need to use a Gradle daemon, the daemon JVM can also be instrumented to start in debug mode:

Gradle System Properties | org.gradle.jvmargs | Attaching a Debugger to a Gradle Daemon

IDE Configuration

https://medium.com/dan-on-coding/debugging-gradle-source-code-in-intellij-e1224bec9b6e

TODO: IntelliJ Gradle Support | Configuring Gradle Sources

• Get sources from GitHub. "Subproject" sources are available in subprojects/bootstrap/src/main/java, subprojects/launcher/src/main/java, etc.
• Script that collects sources and builds a consolidated source JAR file is available here:
  • https://github.com/ovidiuf/shell-tools/blob/master/gradle/package-gradle-sources
  • https://github.com/ovidiuf/playground/blob/master/gradle/tools/build-source-jar
• Attach them to External Libraries → gradle-api-6.2.2.jar → Right click → Open Library Settings → Right click → Edit → +

Gradle runs in IntelliJ

Edit configurations → + → Gradle

Debug a Test Executed with Gradle

Debugging Gradle Tests

Gradle Daemon Operations

Gradle Daemon Operations

TODEPLETE

Operations TODEPLETE