Clean and actionable error reporting

[donat]

Many users reported that it’s hard to investigate Gradle build failures, both in the IDE and on the command line. The existing error messages are verbose and often contain duplications, unhelpful messages are displayed, reports are presented in an inconsistent way, etc. On top of that Gradle does not expose additional details about build failures to the IDEs, and consequently users get little extra help over what’s printed to the command line.

The goal is to provide the missing guidance for failure investigation. Gradle should provide easy-to-understand and actionable information on the nature of the problem. Also, Gradle should provide structured contextual information for further investigation, let it be code references, links to documentation and reports, etc. This new data should be available for IDEs such as IntelliJ IDEA and Android Studio.

References

• Roadmap document

Discuss

• #problems-api on the Community Slack

Status

• API stabilisation and the implementation of the remaining planned features will be finished until the end of 2024.
• Adoption effort should start as part of the stabilisation efforts around the end of 2024.

### Key deliverables
- [ ] https://github.com/gradle/build-tool-roadmap/issues/80
- [ ] https://github.com/gradle/build-tool-roadmap/issues/89
- [ ] https://github.com/gradle/build-tool-roadmap/issues/77
- [ ] https://github.com/gradle/build-tool-roadmap/issues/93
- [ ] https://github.com/gradle/build-tool-roadmap/issues/98
- [ ] https://github.com/gradle/build-tool-roadmap/issues/99
- [ ] https://github.com/gradle/build-tool-roadmap/issues/100
- [ ] https://github.com/gradle/build-tool-roadmap/issues/101
- [ ] https://github.com/gradle/build-tool-roadmap/issues/102