8000 Publish KSP warnings and errors through the Gradle Problems API by ganadist · Pull Request #3288 · google/ksp · GitHub
[go: up one dir, main page]

Skip to content
8000

Publish KSP warnings and errors through the Gradle Problems API - #3288

Draft
ganadist wants to merge 12 commits into
google:mainfrom
ganadist:support_problems_api
Draft

ganadist wants to merge 12 commits into
google:mainfrom
ganadist:support_problems_api

Conversation

@ganadist
Copy link
Copy Markdown

Publish KSP diagnostics through Gradle's Problems API so IDE and CI integrations can consume their severity and source locations.
This builds on the separate BTA diagnostic bridge and keeps processing-engine changes in that prerequisite.

  • Problems reporting requires Gradle 8.13+ and the relevant API classes. When they are unavailable, eligible builds keep BTA console reporting. The KSP BTA opt-out also disables this reporting.
  • Diagnostics retain task context and remain available when startup or processing fails. Distinct locations survive Gradle's problem-summary limit, and console reporting avoids duplicate messages while keeping errors visible with quiet logging.
  • Source files and line numbers are reported without changing KSP's public API. BTA and Problems support columns, but producing them through the public API requires further compatibility decisions; the adapters already accept column information.

Related to #3287
Fixes #2504

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support Gradle Problems API for errors and warnings

1 participant

0