Gradle Operations: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 36: Line 36:


====No Gradle Daemon is Used====
====No Gradle Daemon is Used====
====Gradle Daemon is Used====
{{Internal|Gradle_System_Properties#Attaching_a_Debugger_to_a_Gradle_Daemon|Gradle System Properties | org.gradle.jvmargs | Attaching a Debugger to a Gradle Daemon}}
===Gradle runs in IntelliJ===
===Gradle runs in IntelliJ===
Edit configurations → + → Gradle
Edit configurations → + → Gradle

Revision as of 00:42, 28 March 2021

Internal

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

TODO: IntelliJ Gradle Support | Configuring Gradle Sources

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.

IDE Configuration

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

No Gradle Daemon is Used

Gradle runs in IntelliJ

Edit configurations → + → Gradle

Gradle Daemon Operations

Gradle Daemon Operations

TODEPLETE

Operations TODEPLETE