Merge branch 'PKLIBS-48' into 'master'

It's now possible to override the coding standards per project. One shouldn't bu…

…t it's useful to disable/enable experimental rules once we introduce them.

See merge request !2

build.properties.dist

@@ -1,4 +1,5 @@
 #codestyle
+codestyle.standard = ${project.vendor}/polderknowledge/coding-standards/PolderKnowledge/ruleset.xml
 codestyle.phpcodesniffer.enabled = true
 codestyle.phpdoc.enabled = true
 

common.xml

@@ -55,7 +55,6 @@
         </then>
     </if>
 
-
     <import file="${phing.commons.root}/targets/test/phpunit.xml" />
     <import file="${phing.commons.root}/targets/phpmd/phpmd.xml" />
     <import file="${phing.commons.root}/targets/phpcpd/phpcpd.xml" />
@@ -64,7 +63,6 @@
     <import file="${phing.commons.root}/targets/codestyle/checkstyle.xml" />
     <import file="${phing.commons.root}/targets/phpdoc/phpdoc.xml" />
 
-
     <target name="clean" description="cleans the workspace">
         <delete dir="${project.build}" includeemptydirs="true" failonerror="false" />
     </target>

targets/codestyle/checkstyle.xml

@@ -4,8 +4,9 @@
         <if>
             <equals arg1="${codestyle.phpcodesniffer.enabled}" arg2="true"/>
             <then>
+                <echo message="Checking codestyle using standard ${codestyle.standard}"/>
                 <phpcodesniffer
-                        standard="${project.vendor}/polderknowledge/coding-standards/PolderKnowledge/ruleset.xml"
+                        standard="${codestyle.standard}"
                         format="summary" skipversioncheck="true">
                     <fileset refid="${validation.fileset}"/>
                     <formatter type="full" usefile="false"/>