|Table of content|
The following documentation has been written for Sonar versions >= 2.3.
To understand how rules extensions works on sonar, please refer to Extend coding rules.
Extending php_codesniffer rules
PHP_CodeSniffer is built on an extensible architecture where you can define you own sniffs and thus add some detectors for violations. Out of the box phpcs contains more than 500 rules among hundreds of files. Unfortunatly, the violations associated to the sniffs are not described in a xml file.
So Sonar PHP Plugin team developped a parser that tried to read this violations and put them inside a rules.xml file which is the file format used to describe and extends rules inside sonar.
The drawback is that some sniffs are not detected and maybe missing from the rule repository. Moreover, some people can also develop their own sniffs and of course, these sniffs won't be available in Sonar PHP.
The good news is that since Sonar 2.3 a mechanism for extending rules is present and supported by Sonar PHP Plugin.
To do so, you just have to create your own rules.xml file following these format:
This file must be copied in the directory $SONAR_HOME/extensions/rules/php_codesniffer_rules/. And then, you must restart you sonar instance to make it available for PHP profiles.
Extending PHPMD rules
Extending PHPMD works the same way. Except that you have to copy your file containing your custom violations in $SONAR_HOME/extensions/rules/phppmd_rules/
This XML file must look like the following example :