Hello everyone.
I found this topic so I decided to post my problem here because it's a similar situation.
I'm using SonarLint 2.6.0, SonarQube Server 5.6.5 and Eclipse IDE 4.6.2. All my projects are in "connected mode" and correctly binded to the Server projects. I have disabled the "Run automatically" option for performance reasons.
I found several problems when using SonarLint, that I describe below:
1. When I run SonarLint. some of issues reported in the Server don't appear in SonarLint.
From what I read on this thread, it was supposed that all issues from Sonar Analyzer would also be present in SonarLint.
For instance, I have an issue from rule squid:2259 reported on the server, but not in SonarLint.
I suppose SonarLint downloads the java plugin from server so there should not be any mismatch due to different plugin versions, am I right?
2. I also found some issues were they are both present in Server and in SonarLint, but with different severity, because I changed the default severity on the server. Shouldn't the severity also be the same?
For these two problems I described above, I don't know if there might be something wrongly configured in my IDE.
When I look to the SonarLint console, I find this:
Analyzing 1 changed file(s) in 1 project(s)
Trigger: CHANGESET
SonarLint analysis of project com.mycompany.myproject.core (2 files)...
Binary directory was not added because it was not found. Maybe should you enable auto build of your project.
Binary directory was not added because it was not found. Maybe should you enable auto build of your project.
Binary directory was not added because it was not found. Maybe should you enable auto build of your project.
Binary directory was not added because it was not found. Maybe should you enable auto build of your project.
Binary directory was not added because it was not found. Maybe should you enable auto build of your project.
Binary directory was not added because it was not found. Maybe should you enable auto build of your project.
Binary directory was not added because it was not found. Maybe should you enable auto build of your project.
Binary directory was not added because it was not found. Maybe should you enable auto build of your project.
Binary directory was not added because it was not found. Maybe should you enable auto build of your project.
Binary directory was not added because it was not found. Maybe should you enable auto build of your project.
Connected mode (using configuration of 'abc:com.mycompany.myproject.core' in server 'sonar-main')
Starting analysis with configuration:
[
moduleKey: abc:com.mycompany.myproject.core
baseDir: C:\work\eclipse\main\git\main\src\plugins\com.mycompany.myproject.core
workDir: C:\work\eclipse\main\ws\.metadata\.plugins\org.eclipse.core.resources\.projects\com.mycompany.myproject.core\org.sonarlint.eclipse.core
extraProperties: {sonar.java.source=1.8, sonar.java.target=1.8, ... , sonar.java.binaries=C:/work/eclipse/main/git/main/src/plugins/com.mycompany.myproject.core/bin, ...
inputFiles: [
C:\work\eclipse\main\git\main\src\plugins\com.mycompany.myproject.core\src\com\mycompany\myproject\core\EntityDeleteCommand.java
]
]
Found 113 issue(s)
fetchServerIssues moduleKey=abc:com.mycompany.myproject.core, filepath=src/com/mycompany/myproject/core/EntityDeleteCommand.java
Done in 4760 ms
I don't know if the error of missing binary directory can be the root cause for this.
I also don't understand the reason for this, because everything looks correctly configured, the binary directory is actually there in the log.
I have a proposal for two feature/enhancements, I'm not sure if this is the correct place to do it:
3. Allow the Developer to identify the new issues compared to what is already in the Server; either by toggling between all issues / new issues, or to allow to configure different severity, for instance, I would mark new issues as error/warning, and existing issues as info.
This was possible with the old SonarQube Eclipse plugin, and when switching to the SonarLint plugin, I feel that I loose functionality.
4. Ideally, it would also help to see/filter the assignee because although I agree with "boy scout" approach, sometimes there are too many issues and the Developer wants to focus on the ones that are assigned to him.
best regards,
Silvestre