SonarLint for Eclipse v10.6 brings performance enhancements!

These enhancements, designed to speed up the full-project analysis and lower the memory footprint, target Java and Node.js projects in particular.

Plus, we have added support for STIG metadata in Python and Java.

Check out the release notes and community announcement.

SonarLint for Eclipse v10.5 delivers new rules to detect advanced Java issues, improved secret detection capabilities, plus info on new version availability.

We’ve added in-IDE notifications and direct links to release notes in the Eclipse Welcome tab | overview section, all designed to keep you updated with the latest versions of SonarLint.

Plus, when leveraging the full power of the Sonar solution in connected mode to either SonarCloud or SonarQube you will be able to detect 6 advanced issues that can cause your Java programs to crash.

And finally, we now detect 146 secret patterns of 81 cloud services 💪

Dive into the details with our release notes and community announcement.

SonarLint for Eclipse v10.4 delivers added value for users of SonarCloud. 

With the new Open in IDE button in SonarCloud, you can now open any issue you are investigating in SonarCloud directly into Eclipse with a single click. SonarLint will automatically open the correct file and take you to the line of code containing the issue.

Plus, we have enabled the Clean as You Code methodology, allowing you to focus only on issues in your new code. This incremental approach empowers developers to take ownership of all new code and tackle overall technical debt in a manageable and sustainable manner.

In addition:

• We’ve added support for Eclipse Buildship (Gradle) regarding the exclusion of files in nested modules and the hierarchy for the Shared Connected Mode configuration.

For further details, check out the release notes and community announcement.

SonarLint for Eclipse 10.2 improves support for COBOL and COBOL IDEs, as well as improves SonarLint usage in pre-configured and strict environments. Other notable additions:

• We enabled 21 Java rules on test sources and fixed 8 False-Positives
• For JavaScript/TypeScript, we added 4 accessibility rules

Discover more with our release notes and community announcement. 

SonarLint for Eclipse 10.1 enables enhanced collaboration by introducing sharing Connected Mode setup among contributors as well as new rules and language support.

• We now support JCL, an orchestrator for running COBOL programs
• For Java, we introduced new Java 21 and new sustainability rules
• Python received 14 new rules (4.16 and 4.17)
• Improved Javascript/Typescript with 4 new accessibility rules

Also of note, we are dropping support of NodeJS v16.

Discover more with our release notes and community announcement. 

SonarLint for Eclipse v10.0 introduces a new architecture that relocates the SonarLint business logic from the IDE to a background process and enhances IDE responsiveness.

In addition:

• We’ve added 17 new rules for accessibility in HTML.
• We improved the top dismissed JS/TS rules and added one rule (S2004).
• We fixed 13 false positive rules and added 2 new quick fixes for Python.

For further details, check out the release notes and community announcement.

SonarLint for Eclipse v9.3 enhances the combined power of SonarLint and SonarQube while streamlining the setup process.

Now, a one-click connection setup and project binding option will be shown to a SonarLint for Eclipse developer utilizing the SonarQube “Open in IDE” button to investigate an issue directly in their IDE. This functionality, which requires SonarQube v10.4, assists developers in rapidly examining and resolving issues using SonarLint directly in their Eclipse IDE.

Plus, with their SonarLint for Eclipse v9.3 connected to SonarQube v10.4, developers can now detect custom secrets in their code, directly in their IDE. Using custom rules based on secret patterns defined in SonarQube allows developers to spot secrets before they can be leaked into repositories. (Requires SonarQube Enterprise or Data Center Edition).

Also, when using connected mode to SonarCloud or SonarQube v10.4, it is now possible to mark an issue as “Accepted”. This results in the unresolved issue becoming part of the project’s technical debt.

In addition:

• 5 Spring Boot rules for Java
•  Support for TypeScript 5.3

For further details, check out the release notes and community announcement. For more details on how to set up connected mode check here.

SonarLint for Eclipse v9.1 introduces additional benefits for teams working in connected mode to SonarQube.

With SonarQube v10.3, you can now open any issue you’re investigating in SonarQube directly into the IDE, with just a click of a button, thanks to connected mode. This allows you to leverage SonarLint’s dataflow navigation, rule descriptions, and quick fixes for efficient issue investigation and resolution.

Connected mode for Eclipse delivers shared code quality expectations, deeper issue analysis, smart notifications, and additional language analysis opportunities. Learn more here. 

Also:

• Support for Python 3.12 syntax, and 4 new rules related to Python 3.12 features.
• We added 9 Java rules for Spring Boot.
• We introduced 17 new JavaScript rules for JSX.

For further details, check out the release notes and community announcement.

SonarLint for Eclipse v9.0 introduces additional team benefits when using SonarLint in connected mode to SonarCloud and SonarQube.

Now, with SonarQube v10.2 onwards, you can mark a new issue as Won’t Fix or False Positive without waiting for SonarQube to analyze your branch or pull request. Once SonarLint detects a new issue in your code and you decide not to fix it, you can use SonarLint to change the issue status. The updated status will automatically propagate to SonarQube and to any other contributor using SonarLint in connected mode.

Plus, when using connected mode to SonarCloud, any issue or security hotspot status change made in SonarCloud will be instantly synchronized to your IDE, ensuring you can focus on relevant issues.

Also:

• 6 Java rules dedicated to the Spring framework
• 5 Python rules for the Pandas library
• New JavaScript rules for React

Lastly, this version raised the SonarLint required minimum Java runtime version to 17. See here for more details. 

For further details, check out the release notes and community announcement.

SonarLint for Eclipse v8.1 introduces a new feature supporting the Sonar Clean as You Code methodology. Plus, we have extra rules to detect secrets directly in the IDE and new Python rules for Data Scientists.

SonarLint is pairing up with SonarQube and SonarCloud to deliver the “Focus on new code” feature. Enabled this empowers you to focus only on issues in your new code (i.e., code that has been added or changed according to your new code definition.) 

Supporting the Sonar Clean as You Code approach, this powerful feature is available when SonarLint is working together with SonarQube or SonarCloud in connected mode. Learn how here.

In addition, we have incorporated 42 new rules to detect secrets (API tokens, passwords) within your Cloud applications. This enables the immediate detection of secrets in your code when you add or copy/paste them, before you commit or push the code into a repository. This proactive approach boosts confidence in your code and minimizes exposure.

This latest addition brings the total to 100 different types of secrets spanning 60 cloud providers.

Plus:

• New Python rules to help you write clean scientific code using NumPy
• Lots of new React rules

For further details, check out the release notes and community announcement.