SonarSource is pleased to announce the release of SonarLint for Command Line version 2.0.
This new version brings the connected mode: SonarLint can now use the same configuration as the projects analyzed on your SonarQube instance.
First, quality profile and rules that are used by the SonarQube instance are now retrieved and used by SonarLint.
Third, file and issue exclusions configured on the SonarQube instance are now also applied by SonarLint.
On top of those improvements, SonarLint also enhances the reports that are generated with the description of the rules mentioned in the report.
- “Arrays.stream” should be used for primitive arrays (Bug, performance)
- “Optional” should not be used for parameters (Code Smell, clumsy)
- Double Brace Initialization should not be used (Code Smell, leak)
- Test classes should comply with a naming convention (Code Smell, convention, tests)
- Test methods should comply with a naming convention (Code Smell, convention, tests)
- Underscores should be used to make large numbers readable (Code Smell, convention)
- Function constructors should not be used (Security, clumsy)
- Comma operators should not be used in switch cases (Bugs)
- Precise issue location for all rules