sonarqube5.1.2 | 易学教程

SonarQube MSBuild runner fails on deactivated rule

阅读更多关于 SonarQube MSBuild runner fails on deactivated rule

问题 SonarQube MSBuild runner fails if I deactivate FxCop rule in quality profile: Unable to find the rule key corresponding to the rule config key 'CA1305' in in repository "fxcop". I've bulk-added all the fxcop rules. Added a project. Then then deactivated some rules in quality profile and tried to analyze new project. Even there was NOT any violations of this rule in code - runner still fails with this weird error. 回答1: I suspect that you are somehow importing an FxCop report that contains

How to exclude/ignore referenced project(s) analysis from SonarQube

阅读更多关于 How to exclude/ignore referenced project(s) analysis from SonarQube

问题 I have a solution which has three projects (X,Y,Z). Z referenced in Y , Y in X . When I start Analysis with MSBuild SonarQube Runner on project X, it is analyzing Y and Z as well. Do we have any solution for ignoring recursive analysis ? Note: I can not breakup solution file into multiple solution files & refer dll's rather than projects. 回答1: you can add the tag into ProjectReference 'Y' of your project 'X' configuration. <PropertyGroup Condition=" $(ProjectGuid) != '' AND $(SonarQubeExclude

Sonar Methods should not be empty at the constructor

阅读更多关于 Sonar Methods should not be empty at the constructor

问题 I updated my Sonar to Version 5.1.2, and the issue Methods should not be empty appears on this code: public User() {} public User (String login) { this.login = login; } It seems to be a bug. Am I right? Because this didn't happen before. 回答1: I found this jira, It's a Sonar's Bug. https://jira.sonarsource.com/browse/SONARJAVA-1138 回答2: It really seems to be unexpected behavior. I think it was the ticket response above what caused it. I'm trying to talk to the developer to set the S1186 rule.

Sonar Methods should not be empty at the constructor

阅读更多关于 Sonar Methods should not be empty at the constructor

I updated my Sonar to Version 5.1.2, and the issue Methods should not be empty appears on this code: public User() {} public User (String login) { this.login = login; } It seems to be a bug. Am I right? Because this didn't happen before. I found this jira, It's a Sonar's Bug. https://jira.sonarsource.com/browse/SONARJAVA-1138 It really seems to be unexpected behavior. I think it was the ticket response above what caused it. I'm trying to talk to the developer to set the S1186 rule. If you want to follow: https://jira.sonarsource.com/browse/SONARJAVA-1138 来源： https://stackoverflow.com/questions