Feature description
Add an analysis environment doctor for SpotBugs runs.
The doctor should help users understand whether the extension has enough project information to run SpotBugs correctly. It should surface common setup problems before or after analysis, such as missing build output, classpath issues, unreadable filters, plugin problems, or source mapping issues.
This would make it easier to understand why SpotBugs results are missing, incomplete, or different from another environment.
Alternatives considered
Users can check settings, logs, build output, filters, and plugin paths manually today, but that is difficult and time-consuming.
Additional context
This would be especially useful for Maven and Gradle workspaces where analysis depends on compiled classes and resolved project configuration.
Feature description
Add an analysis environment doctor for SpotBugs runs.
The doctor should help users understand whether the extension has enough project information to run SpotBugs correctly. It should surface common setup problems before or after analysis, such as missing build output, classpath issues, unreadable filters, plugin problems, or source mapping issues.
This would make it easier to understand why SpotBugs results are missing, incomplete, or different from another environment.
Alternatives considered
Users can check settings, logs, build output, filters, and plugin paths manually today, but that is difficult and time-consuming.
Additional context
This would be especially useful for Maven and Gradle workspaces where analysis depends on compiled classes and resolved project configuration.