Gradle Operations
Jump to navigation
Jump to search
Internal
Installation
Command Line
Operations
Debug a Gradle Build
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:
IDE Configuration
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:
- 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
gradle test --debug-jvm
Gradle will suspend execution right before running tests and wait for debugger connection on port 5005.
TODO:
- For selecting specific tests for execution, see https://docs.gradle.org/current/userguide/java_testing.html#simple_name_pattern
- Reconcile with Testing_with_Gradle_Java_Plugin#Debugging_a_Gradle_Test