| Info | ||||
|---|---|---|---|---|
| ||||
|
General questions
I have projects that do not use the required
...
versions of PHPUnit, PHP Depend, etc. What can I do?
If you are able to have several versions of code analysis tool on the same machine, just be make sure that the correct one will be used by maven when launching mvn sonar:sonar.
You also have to ensure make sure that the output file log is compatible with the one specified by the version of the tool you want to use.
I have created my own PHP_CodeSniffer Standard or PHPMD ruleset
...
. Can I use it with the Sonar PHP plugin?
Yes, but with some extra work. Two possible cases :
...
In this case you'll be able to recreate your work directly from the Sonar UI for Quality Profiles
NB As per this version (0.6) you You must check for the presence of your rules in Sonar profiles, as some PHPCS rule description is descriptions are still missing.
If you don't find all of your rules, you simply fall in case 2.
...
In this case you will have to to Extend the PHP coding rules
File exclusions
How do I exclude files from a Sonar analysis?
To exclude files from the PHP analysis, just use the standard "sonar.exclusions" property. For example, in a "sonar-project.properties" file, this would look like:
| Code Block |
|---|
sonar.exclusions=**/Database/**/*.php |
This pattern means: any PHP file located in a source folder which path contains the "Database" folder.
- "**/Database/*.php" would mean: any PHP file directly located in a "Database" folder
- "Database/**/*.php" would mean: any PHP file located in a source folder that starts with a "Database" folder
Please note that the exclusion patterns are relative to the source folder.
...
How do I prevent external tools from analyzing some source files?
Most of the time, using the "sonar.exclusions" property (as explained in the previous question) will be enough to exclude files from being reported by Sonar. However, there might be some cases where one really wants to exclude files from being analysed analyzed by an external tool (may it be PHP_CodeSniffer, PHPMD or PDependPHP Depend):
- a file is badly written and the tool is crashing when analysing analyzing this file, thus preventing Sonar from completing the analysis
- a big number of file files must be excluded and there's no need for the external tools to spend time analysing analyzing files that won't be reported by Sonar
In those these specific cases, you should use the "'sonar.xxxx.argumentLine" ' property of the external tools to manually add the exclusions you want. For instance, for PHP_CodeSniffer, you would add the following property (example given for a "sonar-project.properties" file):
| Code Block |
|---|
sonar.phpCodesniffer.argumentLine=--ignore=Database/*.php |
This would tell PHP_CodeSniffer to ignore every PHP file located in the "Database" folder.
| Note | ||
|---|---|---|
| ||
When specifying exclusions directly for each tool, you should also consider specifying to set the "'sonar.exclusions" ' property accordingly. Otherwise, you may have files with incomplete analysesanalysis. |
Unit tests / PhpUnit integration questions
How do I disable unit test & coverage reporting?
The easiest way to disable unit test reporting is to use the following standard Sonar property (example given for a "sonar-project.properties" file):
| Code Block |
|---|
sonar.dynamicAnalysis=false |
...
