Starting with SonarQube 4.2, multi-language projects are supported, in this case, sonar.language properties should NOT be set in order to trigger multi-language analysis.
But in this plugin, it use project.getLanguageKey() in below line:
int active = profile.getActiveRulesByRepository(CoverityPlugin.REPOSITORY_KEY + "-" + project.getLanguageKey()).size();
Then the value of active will always be false if used in multi-language project.
Suggest to remove the checking for active rules by coverity repository, then this plugin will work both for single language and multi-language projects.
Starting with SonarQube 4.2, multi-language projects are supported, in this case, sonar.language properties should NOT be set in order to trigger multi-language analysis.
But in this plugin, it use project.getLanguageKey() in below line: int active = profile.getActiveRulesByRepository(CoverityPlugin.REPOSITORY_KEY + "-" + project.getLanguageKey()).size();
Then the value of active will always be false if used in multi-language project.
Suggest to remove the checking for active rules by coverity repository, then this plugin will work both for single language and multi-language projects.