Right-click a task in Buildship's Gradle Tasks view and choose "Debug Gradle Tasks": the build runs as usual and the debugger is attached to every JVM it forks. Breakpoints work in application code started by JavaExec tasks (run, bootRun, custom server launchers) and in tests.

Features
- "Debug Gradle Tasks" in the context menu of the Gradle Tasks view, for one or more tasks.
- Debug mode for every Buildship "Gradle Task" run configuration, from the Debug toolbar and Debug Configurations.
- Every forked JVM connects to Eclipse on a free port: no Remote Java Application, no Launch Group, no fixed debug port, several JVMs at once (e.g. parallel test workers).
- Hot code replace with the classes Gradle compiles: when you save a Java file, its project is compiled by Gradle and the changed classes are replaced in the running JVM, lambdas included.
- Stopping the "Gradle build" entry in the Debug view stops the build and its JVMs.
- Works with the Gradle configuration cache, which stays reusable from one debug session to the next.

How it works
Eclipse listens for debuggee JVMs, and Buildship runs the build with an init script that starts every task implementing JavaForkOptions with the JDWP agent in client mode, pointing to Eclipse. Your build scripts are not changed.

Requirements: Eclipse 2024-06 or later with Buildship 3.1 or later (included in the Eclipse IDE packages), Java 17 or later, Gradle 5.6 or later for full support.

Open source under the Eclipse Public License 2.0. Feedback and issues are welcome on GitHub.

https://github.com/legrottagliegionata/eclipse-gradle-debug