The Gradle Tooling API now exposes problem reports via Tooling API events. This change implements a listener consuming problem events an converting them to Eclipse error markers.
The feature is not enabled by default. Users need to explicitly opt-in for the time being.
Reported problems show up in the Eclipse Problems view under the Gradle Problem type. The reports are cleared and recreated for every build invocation (sync and task execution).
The error marker has a custom properties page with the report details. Documentation links are navigable and there's a button for copying the stacktrace, just like on the generic Eclipse marker properties page.
The Gradle Tooling API now exposes problem reports via Tooling API events. This change implements a listener consuming problem events an converting them to Eclipse error markers.
The feature is not enabled by default. Users need to explicitly opt-in for the time being.
Reported problems show up in the Eclipse Problems view under the
Gradle Problem
type. The reports are cleared and recreated for every build invocation (sync and task execution).The error marker has a custom properties page with the report details. Documentation links are navigable and there's a button for copying the stacktrace, just like on the generic Eclipse marker properties page.
Tasks