Hi Julien/Simon, Thank you for picking it up and assigning to the correct project. I apologise for filing it against Sonar Maven Plugin in the first place: I had a vague recollection that in general Sonar issues were managed differently, but could not figure out the proper way to do that. I think that it would be very beneficial if each of the following pages: * http://docs.codehaus.org/display/SONAR/Jenkins+Plugin * https://github.com/SonarSource/jenkins-sonar-plugin * http://jira.codehaus.org/browse/SONARJNKNS ...had a promiment paragraph of text explaining that the users should refer to one of the following pages if they want to raise issues with SonarQube team: * http://www.sonarqube.org/get-involved/ * http://www.sonarqube.org/get-support/ The same applies to all other SonarQube projects, including the front page for SONAR Jira project and the Jira/Confluence/MavenSite for Sonar Maven Plugin. I hope that it will help to a certain extent reduce the amount of incorrectly raised issues.
Kind regards, -- Sergei Ivanov Tue, 3 Jun 2014 15:51:10 -0500 (CDT) от "Julien HENRY (JIRA)" <j...@codehaus.org>: >Julien HENRY assigned an issue to Julien HENRY > >SonarQube Jenkins / SONARJNKNS-204 >Jenkins Sonar plugin does not use node-specific tool paths >Change By: Julien HENRY >Assignee: Simon Brandhof Julien HENRY >Add Comment > >This message was sent by Atlassian JIRA (v6.1.6#6162- sha1:7af547c )
