Sonarlint in Eclipse Oxygen (4.7.3)

Hi there,

  • Operating system: Windows 10
  • SonarLint plugin version: :person_shrugging:
  • Programming language you’re coding in: Java

I would like to ask how i can install / work with sonarlint in eclipse 4.7.3 (oxygen) ? (I just read this already closed Thread about Sonarlint 7.3.1)

Use Case is a rather old installation of RAD which is based on oxygen … and i would like to install sonarlint in it. How should i proceed here?


Hi @daniel,

For such an old version of Eclipse, you will have to stay with an old version of SonarLint.

This is not a supported use case (not sure if the connected mode will work for example), but you can give it a try. I think SonarLint 6.2 was the latest version supporting Oxygen. You can install it by using this update site:

1 Like

Thank you for the prompt reply, Julien! I am really curious how well the aged setup will actually work.

Will followup with feedback :nerd_face:

//edit: just as a short feedback:

  • :white_check_mark: configuring the Binding in “Sonarlint Bindings” did work
  • :white_check_mark: Fetching Server Side Findings probably worked :person_shrugging: (no errors in log + Last Storage Update: 26.10.22 : 16:38)
  • :negative_squared_cross_mark: Displaying the synchronized Findings (with active Binding to SQ Server on premise) did not work
  • :white_check_mark: Displaying Findings from local analyze (after removal of active Binding to SQ Server) worked, but - as is expected - with the “default” ruleset of that old plugin version

So, sadly, your doubt concerning connected mode between old SonarLint Plugin and new SonarQube Server (9.6.1) was correct :slight_smile:

Is there anything interesting in the SonarLint Console with verbose logs enabled?

Thank you for pointing me to the verbose debug logging :+1: That in itself is helpful already in dissecting the process.

I understand it as that in connected mode the analysis fails because the java-plugin from sq-server loaded and used (sonar-java-plugin- - which is no more java 8 compatible) versus in standalone mode the internally supplied java-plugin is used (sonar-java-plugin- - which is java 8 compatible)

But that were logentries concerning the analysis … I could not find any helpful hints why in connected mode the already serverside-stored findings would not be displayed in the older sonarlint views. :person_shrugging:

In the log i found entries that state that the server side issues were downloaded:

GET 200 https://sonarqube-instance/batch/issues?key=project.key | response time=359ms
Downloaded issues in 359ms

My current assumption is as follows:

  • After the issues are downloaded,
  • an analysis with the supplied server-config (with newer java-plugin) is triggered
  • which skips/removes “java-stuff” because of incompatibility with java 8
  • and henceforth does not display any downloaded matching java issues (because it excluded java from the results)

Does that make sense to you? :face_with_raised_eyebrow:

That’s correct!

This is because it is not a feature of SonarLint :). SonarLint doesn’t display server-side issues. SonarLint downloads server-side issues only to perform “issue tracking” (match local and server-side issues, in order to merge some attributes, like severity, suppression, …). There is an exception with taint vulnerabilities, but I think we can ignore that for the moment.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.