[mojo-dev] [jira] (MSONAR-70) Use every available "sonar.*" property when running an analysis with Maven

[Juan Ignacio Barisich (JIRA)]

Title: Message Title

Juan Ignacio Barisich commented on an issue   Re: Use every available "sonar.*" property when running an analysis with Maven We have a lot of projects analized with Sonar via Jenkins. Already we are using Sonar 4.1 and we are planning to upgrade to 4.2 for multilanguage support. According the documentation (http://docs.codehaus.org/display/SONAR/Analyzing+with+Maven) it is necessary to define the property sonar.sources=src, but only is possible to set it in the pom file. This is no practicable for us (remember we have a lot of projects). So, we need to set this property via command line, specifically via a Jenkins job property. We hope this feature to be implemented soon. Regards, Add Comment   Mojo's Sonar Maven Plugin / MSONAR-70 Use every available "sonar.*" property when running an analysis with Maven When running an analysis with Maven, some SonarQube properties are always ignored because SonarQube internally feeds them from the POM. Those properties are (non exhaustive list): - sonar.projectKey - sonar.projectName - sonar.projectVersion - sonar.projectDescription - sonar.sources - sonar.tests - sonar.binaries - sonar.libraries - ... (there m... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email