Skip to content

Exposing properties like compiled classes and libraries for SonarLint integration #934

Description

@ChrisTrenkamp

The Java plugin is almost at the point where I can use VSCode full-time. However, it's missing SonarLint Java support, which I feel dramatically increases productivity.

Some people tried to get Java support added to the SonarQube VSCode Plugin, but was not accepted. This is their response: SonarSource/sonarlint-vscode#28 (comment).

They need access to your compiled classes and imported libraries in order for it to be useful. https://docs.sonarqube.org/display/PLUG/Java+Plugin+and+Bytecode

Is it possible to expose these properties for consumption for other plugins? I imagine there's other tools besides SonarLint/SonarQube that need these kinds of properties as well.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions