# SonarLint for Eclipse Stops marking up source files

**URL:** <https://community.sonarsource.com/t/sonarlint-for-eclipse-stops-marking-up-source-files/4509>\
**Category:** Eclipse\
**Tags:** eclipse, sonarqube-ide, java\
**Created:** [November 22, 2018, 3:48pm UTC](https://community.sonarsource.com/t/sonarlint-for-eclipse-stops-marking-up-source-files/4509 "2018-11-22T15:48:22Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![kevinwhine](https://avatars.discourse-cdn.com/v4/letter/k/439d5e/32.png) [@kevinwhine](https://community.sonarsource.com/u/kevinwhine)\
**Post date:** [November 22, 2018, 3:48pm UTC](https://community.sonarsource.com/t/sonarlint-for-eclipse-stops-marking-up-source-files/4509/1 "2018-11-22T15:48:22Z")

</div>

Folks,

I have recently updated my Eclipse to

Version: 2018-09 (4.9.0)  
Build id: 20180917-1800

and SonarLint version 4.0.0.201810170711.

I have Java and Javascript projects bound to an internal sonar server.

When I look on the Sonar server UI there are many issues, but SonarLint does not mark out any issues.

The editor window does not have any SonarLint markup and SonarLint \> Analyze \> Progress table shows an empty grid with the expected number of files being called out

Installation details

| Buildship: Eclipse Plug-ins for Gradle | 2.2.1.v20180125-1441 | org.eclipse.buildship.feature.group | Eclipse Buildship |
| --- | --- | --- | --- |
| Code Recommenders for Java Developers | 2.5.4.v20180909-1132 | org.eclipse.recommenders.rcp.feature.feature.group | Eclipse Code Recommenders |
| Code Recommenders Mylyn Integration | 2.5.4.v20180909-1132 | org.eclipse.recommenders.mylyn.rcp.feature.feature.group | Eclipse Code Recommenders |
| Code Recommenders News Feed | 2.5.4.v20180909-1132 | org.eclipse.recommenders.news.rcp.feature.feature.group | Eclipse Code Recommenders |
| Code Recommenders Snipmatch | 2.5.4.v20180909-1132 | org.eclipse.recommenders.snipmatch.rcp.feature.feature.group | Eclipse Code Recommenders |
| EclEmma Java Code Coverage | 3.1.1.201809121651 | org.eclipse.eclemma.feature.feature.group | Eclipse EclEmma |
| Eclipse Groovy Development Tools | 3.2.0.xx-201811182243-e49 | org.codehaus.groovy.eclipse.feature.feature.group | Pivotal Software, Inc. |
| Eclipse IDE for Java Developers | 4.9.0.20180917-1800 | epp.package.java | Eclipse Packaging Project |
| Eclipse Java Development Tools | 3.15.0.v20180906-0745 | org.eclipse.jdt.feature.group | [Eclipse.org](http://Eclipse.org) |
| Eclipse JDT Core patch for Groovy | 3.2.0.xx-201811182243-e49 | org.codehaus.groovy.jdt.patch.feature.group | Pivotal Software, Inc. |
| Eclipse Platform | 4.9.0.v20180906-1121 | org.eclipse.platform.feature.group | [Eclipse.org](http://Eclipse.org) |
| Eclipse RCP | 4.9.0.v20180906-1121 | org.eclipse.rcp.feature.group | [Eclipse.org](http://Eclipse.org) |
| Eclipse Web Developer Tools | 3.11.0.v201808220605 | org.eclipse.wst.web\_ui.feature.feature.group | Eclipse Web Tools Platform |
| Eclipse XML Editors and Tools | 3.11.0.v201807252207 | org.eclipse.wst.xml\_ui.feature.feature.group | Eclipse Web Tools Platform |
| Git integration for Eclipse | 5.1.0.201809111528-r | org.eclipse.egit.feature.group | Eclipse EGit |
| Git integration for Eclipse - Task focused interface | 5.1.0.201809111528-r | org.eclipse.egit.mylyn.feature.group | Eclipse EGit |
| Groovy Compiler 2.5 | 3.2.0.xx-201811182243-e49 | org.codehaus.groovy25.feature.feature.group | Pivotal Software, Inc. |
| Java implementation of Git | 5.1.0.201809111528-r | org.eclipse.jgit.feature.group | Eclipse JGit |
| JavaScript Development Tools | 2.1.1.v201804042202 | org.eclipse.wst.jsdt.feature.feature.group | Eclipse Web Tools Platform |
| m2e - Maven Integration for Eclipse (includes Incubating components) | 1.9.1.20180912-1601 | org.eclipse.m2e.feature.feature.group | [Eclipse.org](http://Eclipse.org) - m2e |
| m2e - slf4j over logback logging (Optional) | 1.9.1.20180912-1601 | org.eclipse.m2e.logback.feature.feature.group | [Eclipse.org](http://Eclipse.org) - m2e |
| Marketplace Client | 1.7.2.v20180829-1931 | org.eclipse.epp.mpc.feature.group | Eclipse Marketplace Client |
| Mylyn Builds Connector: Hudson/Jenkins | 1.16.0.v20180403-2055 | org.eclipse.mylyn.hudson.feature.group | Eclipse Mylyn |
| Mylyn Context Connector: Eclipse IDE | 3.24.2.v20180905-0014 | org.eclipse.mylyn.ide\_feature.feature.group | Eclipse Mylyn |
| Mylyn Context Connector: Java Development | 3.24.2.v20180905-0014 | org.eclipse.mylyn.java\_feature.feature.group | Eclipse Mylyn |
| Mylyn Task List | 3.24.2.v20180905-0003 | org.eclipse.mylyn\_feature.feature.group | Eclipse Mylyn |
| Mylyn Task-Focused Interface | 3.24.2.v20180905-0014 | org.eclipse.mylyn.context\_feature.feature.group | Eclipse Mylyn |
| Mylyn Tasks Connector: Bugzilla | 3.24.2.v20180905-0003 | org.eclipse.mylyn.bugzilla\_feature.feature.group | Eclipse Mylyn |
| Mylyn Versions Connector: Git | 1.16.0.v20170629-1738 | org.eclipse.mylyn.git.feature.group | Eclipse Mylyn |
| Mylyn WikiText | 3.0.25.201806201740 | org.eclipse.mylyn.wikitext\_feature.feature.group | Eclipse Mylyn |
| Oomph Setup | 1.11.0.v20181107-0652 | org.eclipse.oomph.setup.feature.group | Eclipse Oomph Project |
| SonarLint for Eclipse | 4.0.0.201810170711 | org.sonarlint.eclipse.feature.feature.group | SonarSource |
| Tip of the Day UI Feature | 0.2.100.v20180821-0700 | org.eclipse.tips.feature.feature.group | Remain Software |

---

<div class="post-metadata">

**Author:** ![anon67236913](https://avatars.discourse-cdn.com/v4/letter/a/c37758/32.png) [@anon67236913](https://community.sonarsource.com/u/anon67236913)\
**Post date:** [November 23, 2018, 7:39am UTC](https://community.sonarsource.com/t/sonarlint-for-eclipse-stops-marking-up-source-files/4509/2 "2018-11-23T07:39:46Z")

</div>

Hi Kevin,  
SLE supports only a specific subset of analyzers.  
From [https://www.sonarlint.org/eclipse/](https://www.sonarlint.org/eclipse/)  
Java, Javascript,Php, Python  
Also what is the version of your Sonarqube server ?  
SLE 4.0.0 works only with later versions of analyzers, that are available for Sonarqube server \> 5.6.x  
See [releasenotes SLE 4.0.0](https://jira.sonarsource.com/browse/SLCORE/fixforversion/14582/?selectedTab=com.atlassian.jira.plugins.jira-development-integration-plugin:release-report-tabpanel) first entry.  
If this is the case, your SLE console will have several entries like that:  
`Code analyzer '...' version '...' is not supported (minimal version is '...'). Skip downloading it.`  
And after editing a file of a project with a binding to a SQ Server \< 6.x console has:

```
No language available
No analyzers installed
Start analysis
Index files
1 files indexed
Quality profiles:
Found 0 issue(s)

```

Regards,  
Gilbert

---

<div class="post-metadata">

**Author:** ![kevinwhine](https://avatars.discourse-cdn.com/v4/letter/k/439d5e/32.png) [@kevinwhine](https://community.sonarsource.com/u/kevinwhine)\
**Post date:** [November 23, 2018, 9:34am UTC](https://community.sonarsource.com/t/sonarlint-for-eclipse-stops-marking-up-source-files/4509/3 "2018-11-23T09:34:20Z")

</div>

Hi Gilbert,

Thanks for your response!

I am binding to SonarQube server that has " SonarQube™ technology is powered by [SonarSource SA](http://www.sonarsource.com/) Version 6.2 - [LGPL v3](http://www.gnu.org/licenses/lgpl-3.0.txt) - [Community]" at the footer of its about page.

I am analysing Java and Javascript projects only. I have had successful analysis on previous EClipse versions eg Oxygen and previous versions of SonarLint for Eclipse. The SonarQube server has not changed. Is my understanding correct when I say the SQ API would be greater 5.6, or do I need to make further checks?

When I change a file I see no SonarLint activity.  
When Java Project \> SonarLInt \> Analyze I see:

- The progress tab shows the SonarLInt activity
- The console tab remains unchanged
- The SonarLint Report tab is displayed with a blank/empty grid with 0 Items. The number of files and timestamp are at the bottom.

This morning I tried a Javascript project \> SonarLInt \> Analyze and it is processing for 1o minutes at 0% complete.

When I check Eclipse \> Window \> Show View \> Error Log I do not see any entries added (SLE Or other)

In previous configurations I did see SonarLint activity in the console tab, but not now.

I am sure I have some configuration wrong.

---

<div class="post-metadata">

**Author:** ![anon67236913](https://avatars.discourse-cdn.com/v4/letter/a/c37758/32.png) [@anon67236913](https://community.sonarsource.com/u/anon67236913)\
**Post date:** [November 23, 2018, 9:55am UTC](https://community.sonarsource.com/t/sonarlint-for-eclipse-stops-marking-up-source-files/4509/4 "2018-11-23T09:55:05Z")

</div>

Hi Kevin,  
just a guess, is Eclipse project / properties “Run SonarLint automatically” activated ?  
If your Eclipse project or package or file has a substring ‘test’ it may be affected from the global SLE settings, see Window/Preferences/SonarLint/Test file regular expression.  
Also check your SLE console - set Verbose output - for entries like that, to make sure your SQ server doesn’t use incompatible version of analyzers:

```
Code analyzer 'plsql' version '3.0.1.1427' is not supported (minimal version is '3.1'). Skip downloading it.
 Code analyzer 'java' version '4.15.0.12310' is not supported (minimal version is '5.1'). Skip downloading it.
 Code analyzer 'web' version '2.5.0.476' is not supported (minimal version is '2.6'). Skip downloading it.
 Code analyzer 'typescript' version '1.1.0.1079' is not supported (minimal version is '1.5'). Skip downloading it.
 Code analyzer 'swift' version '3.0.0.1969' is not supported (minimal version is '3.1'). Skip downloading it.
 Code analyzer 'cpp' version '4.14.0.9331' is not supported (minimal version is '5.0'). Skip downloading it.
 Code analyzer 'python' version '1.8.0.1496' is not supported (minimal version is '1.9.1'). Skip downloading it.
 Code analyzer 'javascript' version '3.3.0.5702' is not supported (minimal version is '4.0'). Skip downloading it.

```

Regards,  
Gilbert

---

<div class="post-metadata">

**Author:** ![kevinwhine](https://avatars.discourse-cdn.com/v4/letter/k/439d5e/32.png) [@kevinwhine](https://community.sonarsource.com/u/kevinwhine)\
**Post date:** [November 23, 2018, 10:33am UTC](https://community.sonarsource.com/t/sonarlint-for-eclipse-stops-marking-up-source-files/4509/5 "2018-11-23T10:33:20Z")

</div>

Hi Gilbert,

That is it. The versions installed are

· SonarJava **4.5.0.8398** installed

· SonarJS **2.18.0.3454** installed

So those are not going to work. I will put in a request to update them. But what version of SonarLint will support those plugin versions?

Kevin

---

<div class="post-metadata">

**Author:** ![anon67236913](https://avatars.discourse-cdn.com/v4/letter/a/c37758/32.png) [@anon67236913](https://community.sonarsource.com/u/anon67236913)\
**Post date:** [November 23, 2018, 10:39am UTC](https://community.sonarsource.com/t/sonarlint-for-eclipse-stops-marking-up-source-files/4509/6 "2018-11-23T10:39:24Z")

</div>

Hi Kevin,  
SLE 3.6.0 will probably work with this versions. But it is recommended to use the latest versions of analyzers, because of new rules, bugfixes, better performance … etc.  
Your versions are rather old, Sonar Java has 5.9.1 now, SonarJS 5.0  
With SQ 6.7.5 LTS or SQ 7.4 refined ruleimplementations won’t affect legacy code due to issue backdating, so no problems here. Just update the analyzers in your SQ staging/test instance and see if it works for you.  
With the latest analyzers you may also use SLE 4.0.0  
Regards,  
Gilbert

---

<div class="post-metadata">

**Author:** ![kevinwhine](https://avatars.discourse-cdn.com/v4/letter/k/439d5e/32.png) [@kevinwhine](https://community.sonarsource.com/u/kevinwhine)\
**Post date:** [November 23, 2018, 10:51am UTC](https://community.sonarsource.com/t/sonarlint-for-eclipse-stops-marking-up-source-files/4509/7 "2018-11-23T10:51:27Z")

</div>

Thanks Gilbert. This issue is resolved until I get those versions updated.

Kevin
