Feature description
Add a way to import existing Eclipse SpotBugs or FindBugs project settings into the VS Code extension.
Some Java projects already use SpotBugs or FindBugs in Eclipse. When those projects are opened in VS Code, users should not have to recreate the same settings manually.
The extension should detect existing Eclipse SpotBugs/FindBugs settings when available and help import the supported options into VS Code. This could include analysis effort, warning level, filters, plugins, and other matching settings.
If some settings cannot be imported, the extension should clearly show them instead of ignoring them silently.
Alternatives considered
Users can manually copy matching settings into VS Code, but that is easy to miss and can make SpotBugs behave differently between Eclipse and VS Code.
Additional context
This would make migration from Eclipse to VS Code easier and help teams keep SpotBugs behavior consistent across IDEs.
Feature description
Add a way to import existing Eclipse SpotBugs or FindBugs project settings into the VS Code extension.
Some Java projects already use SpotBugs or FindBugs in Eclipse. When those projects are opened in VS Code, users should not have to recreate the same settings manually.
The extension should detect existing Eclipse SpotBugs/FindBugs settings when available and help import the supported options into VS Code. This could include analysis effort, warning level, filters, plugins, and other matching settings.
If some settings cannot be imported, the extension should clearly show them instead of ignoring them silently.
Alternatives considered
Users can manually copy matching settings into VS Code, but that is easy to miss and can make SpotBugs behave differently between Eclipse and VS Code.
Additional context
This would make migration from Eclipse to VS Code easier and help teams keep SpotBugs behavior consistent across IDEs.