diff --git a/pmd-plsql/src/main/resources/rulesets/plsql/TomKytesDespair.xml b/pmd-plsql/src/main/resources/rulesets/plsql/TomKytesDespair.xml
index 44f45a03a5..b7147f6af4 100644
--- a/pmd-plsql/src/main/resources/rulesets/plsql/TomKytesDespair.xml
+++ b/pmd-plsql/src/main/resources/rulesets/plsql/TomKytesDespair.xml
@@ -3,73 +3,74 @@
     xmlns="http://pmd.sourceforge.net/ruleset/2.0.0"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://pmd.sourceforge.net/ruleset/2.0.0 http://pmd.sourceforge.net/ruleset_2_0_0.xsd">
-<description>
-    Rules based on Thomas Kyte's recommendations on http://asktom.oracle.com/ and http://tkyte.blogspot.com/.
-</description>
 
-<rule  language="plsql" name="TomKytesDespair"
-  since="5.1"
-  message="WHEN OTHERS THEN NULL - when you do this, Tom Kyte cries"
-  class="net.sourceforge.pmd.lang.rule.XPathRule"
-  externalInfoUrl="${pmd.website.baseurl}/rules/plsql/TomKytesDespair.html#TomKytesDespair">
   <description>
-  "WHEN OTHERS THEN NULL" hides all errors - (Re)RAISE an exception or call RAISE_APPLICATION_ERROR 
+Rules based on Thomas Kyte's recommendations on http://asktom.oracle.com/ and http://tkyte.blogspot.com/.
   </description>
-  <priority>3</priority>
-  <properties>
-    <property name="xpath">
-    <value>
+
+  <rule name="TomKytesDespair"
+        language="plsql"
+        since="5.1"
+        message="WHEN OTHERS THEN NULL - when you do this, Tom Kyte cries"
+        class="net.sourceforge.pmd.lang.rule.XPathRule"
+        externalInfoUrl="${pmd.website.baseurl}/pmd_rules_plsql_TomKytesDespair.html#tomkytesdespair">
+    <description>
+"WHEN OTHERS THEN NULL" hides all errors - (Re)RAISE an exception or call RAISE_APPLICATION_ERROR 
+    </description>
+    <priority>3</priority>
+    <properties>
+        <property name="xpath">
+            <value>
 <![CDATA[
 //ExceptionHandler[QualifiedName/@Image='OTHERS' and upper-case(Statement/UnlabelledStatement/Expression/@Image)='NULL']
-
 ]]>
-    </value>
-    </property>
-  </properties>
-  <example>
+            </value>
+        </property>
+    </properties>
+    <example>
 <![CDATA[
 CREATE OR REPLACE PACKAGE BODY update_planned_hrs
 IS
- 
+
 PROCEDURE set_new_planned (p_emp_id IN NUMBER, p_project_id IN NUMBER, p_hours IN NUMBER)
 IS
 BEGIN
    UPDATE employee_on_activity ea
    SET ea.ea_planned_hours = p_hours
    WHERE
-            ea.ea_emp_id = p_emp_id            
+            ea.ea_emp_id = p_emp_id
             AND ea.ea_proj_id = p_project_id;
- 
+
 EXCEPTION
           WHEN NO_DATA_FOUND THEN
-           RAISE_APPLICATION_ERROR (-20100, 'No such employee or project');
- 
+          RAISE_APPLICATION_ERROR (-20100, 'No such employee or project');
+
 END set_new_planned;
- 
+
 FUNCTION existing_planned (p_emp_id IN NUMBER, p_project_id IN NUMBER) RETURN NUMBER
- 
+
 IS
- 
+
 existing_hours NUMBER(4);
- 
+
 BEGIN
-   SELECT ea.ea_planned_hours INTO existing_hours 
+   SELECT ea.ea_planned_hours INTO existing_hours
    FROM employee_on_activity ea
    WHERE
-            ea.ea_emp_id = p_emp_id     
-            AND ea.ea_proj_id = p_project_id; 
- 
+            ea.ea_emp_id = p_emp_id
+            AND ea.ea_proj_id = p_project_id;
+
    RETURN (existing_hours);
- 
+
    EXCEPTION
           WHEN OTHERS THEN NULL;
- 
+
    END existing_planned;
- 
+
 END update_planned_hrs;
 /
 ]]>
-  </example>
-</rule>
-</ruleset>
+    </example>
+  </rule>
 
+</ruleset>
diff --git a/pmd-plsql/src/main/resources/rulesets/plsql/codesize.xml b/pmd-plsql/src/main/resources/rulesets/plsql/codesize.xml
index 7079e59dde..a0b80cbc43 100644
--- a/pmd-plsql/src/main/resources/rulesets/plsql/codesize.xml
+++ b/pmd-plsql/src/main/resources/rulesets/plsql/codesize.xml
@@ -8,394 +8,387 @@
 The Code Size ruleset contains rules that find problems related to code size or complexity.
   </description>
 
-<rule name="NPathComplexity"
-      language="plsql"
-      since="5.1"
-      message="The method {0}() has an NPath complexity of {1}"
-      class="net.sourceforge.pmd.lang.plsql.rule.codesize.NPathComplexityRule"
-      externalInfoUrl="${pmd.website.baseurl}/rules/plsql/codesize.html#NPathComplexity">
-   <description>
+  <rule name="NPathComplexity"
+        language="plsql"
+        since="5.1"
+        message="The method {0}() has an NPath complexity of {1}"
+        class="net.sourceforge.pmd.lang.plsql.rule.codesize.NPathComplexityRule"
+        externalInfoUrl="${pmd.website.baseurl}/pmd_rules_plsql_codesize.html#npathcomplexity">
+    <description>
 The NPath complexity of a method is the number of acyclic execution paths through that method.
 A threshold of 200 is generally considered the point where measures should be taken to reduce 
 complexity and increase readability.
-   </description>
-     <priority>3</priority>
+    </description>
+    <priority>3</priority>
     <example>
- <![CDATA[
+<![CDATA[
 CREATE OR REPLACE
-PROCEDURE bar AS BEGIN	-- this is something more complex than it needs to be,
-	if (y) THEN	-- it should be broken down into smaller methods or functions
-		for j IN 0 .. j-1 LOOP
-			if (j > r) THEN
-				doSomething;
-				while (f < 5 ) LOOP
-					anotherThing;
-					f := f - 27;
-					END LOOP;
-			else
-					tryThis();
-			END IF;
-		END LOOP;
-	END IF;
-	if ( r - n > 45) THEN
-		while (doMagic) LOOP
-			findRabbits;
-		END LOOP;
-	END IF;
-	BEGIN
-		doSomethingDangerous();
-	EXCEPTION WHEN FooException THEN
-		makeAmends;
-		BEGIN
-			dontDoItAgain;
-		EXCEPTION
-		WHEN OTHERS THEN
-				log_problem;
-		END;
-	END;
+PROCEDURE bar AS BEGIN  -- this is something more complex than it needs to be,
+    if (y) THEN -- it should be broken down into smaller methods or functions
+        for j IN 0 .. j-1 LOOP
+            if (j > r) THEN
+                doSomething;
+                while (f < 5 ) LOOP
+                    anotherThing;
+                    f := f - 27;
+                    END LOOP;
+            else
+                tryThis();
+            END IF;
+        END LOOP;
+    END IF;
+    if ( r - n > 45) THEN
+        while (doMagic) LOOP
+            findRabbits;
+        END LOOP;
+    END IF;
+    BEGIN
+        doSomethingDangerous();
+    EXCEPTION WHEN FooException THEN
+        makeAmends;
+        BEGIN
+            dontDoItAgain;
+        EXCEPTION
+        WHEN OTHERS THEN
+            log_problem;
+        END;
+    END;
 END;
-
- ]]>
+]]>
     </example>
-</rule>
+  </rule>
 
- <rule name="ExcessiveMethodLength"
-      language="plsql"
- 		 since="5.1"
-		 message="Avoid really long methods ({0} lines found)."
-       class="net.sourceforge.pmd.lang.plsql.rule.codesize.ExcessiveMethodLengthRule"
-       externalInfoUrl="${pmd.website.baseurl}/rules/plsql/codesize.html#ExcessiveMethodLength">
-   <description>
+  <rule name="ExcessiveMethodLength"
+        language="plsql"
+        since="5.1"
+        message="Avoid really long methods ({0} lines found)."
+        class="net.sourceforge.pmd.lang.plsql.rule.codesize.ExcessiveMethodLengthRule"
+        externalInfoUrl="${pmd.website.baseurl}/pmd_rules_plsql_codesize.html#excessivemethodlength">
+    <description>
 When methods are excessively long this usually indicates that the method is doing more than its
 name/signature might suggest. They also become challenging for others to digest since excessive 
 scrolling causes readers to lose focus.
 Try to reduce the method length by creating helper methods and removing any copy/pasted code.
-   </description>
-     <priority>3</priority>
-   <example>
+    </description>
+    <priority>3</priority>
+    <example>
 <![CDATA[
 CREATE OR REPLACE
 PROCEDURE doSomething BEGIN
-	DBMS_OUTPUT.PUT_LINE("Hello world!");
-	DBMS_OUTPUT.PUT_LINE("Hello world!");
-		-- 98 copies omitted for brevity.
+    DBMS_OUTPUT.PUT_LINE("Hello world!");
+    DBMS_OUTPUT.PUT_LINE("Hello world!");
+        -- 98 copies omitted for brevity.
 END;
-
 ]]>
-   </example>
+    </example>
+  </rule>
 
- </rule>
-
-
- <rule name="ExcessiveParameterList"
-      language="plsql"
- 		 since="5.1"
-       message="Avoid long parameter lists."
-       class="net.sourceforge.pmd.lang.plsql.rule.codesize.ExcessiveParameterListRule"
-          externalInfoUrl="${pmd.website.baseurl}/rules/plsql/codesize.html#ExcessiveParameterList">
-   <description>
+  <rule name="ExcessiveParameterList"
+        language="plsql"
+        since="5.1"
+        message="Avoid long parameter lists."
+        class="net.sourceforge.pmd.lang.plsql.rule.codesize.ExcessiveParameterListRule"
+        externalInfoUrl="${pmd.website.baseurl}/pmd_rules_plsql_codesize.html#excessiveparameterlist">
+    <description>
 Methods with numerous parameters are a challenge to maintain, especially if most of them share the
 same datatype. These situations usually denote the need for new objects to wrap the numerous parameters.
-   </description>
-     <priority>3</priority>
-   <example>
+    </description>
+    <priority>3</priority>
+    <example>
 <![CDATA[
 CREATE OR REPLACE
-PROCEDURE addPerson(		-- too many arguments liable to be mixed up
-	birthYear pls_integer, birthMonth pls_integer, birthDate pls_integer, height pls_integer, weight pls_integer, ssn pls_integer) {
+PROCEDURE addPerson(        -- too many arguments liable to be mixed up
+    birthYear pls_integer, birthMonth pls_integer, birthDate pls_integer, height pls_integer, weight pls_integer, ssn pls_integer) {
 
-	. . . .
+    . . . .
 END ADDPERSON;
- 
-CREATE OR REPLACE
-PROCEDURE addPerson(		-- preferred approach
-	birthdate DATE, measurements BodyMeasurements , ssn INTEGER) BEGIN
 
-	. . . .
+CREATE OR REPLACE
+PROCEDURE addPerson(        -- preferred approach
+    birthdate DATE, measurements BodyMeasurements , ssn INTEGER) BEGIN
+
+    . . . .
 END;
 ]]>
-   </example>
+    </example>
+  </rule>
 
- </rule>
-
- <rule name="ExcessiveObjectLength"
-      language="plsql"
- 		 since="5.1"
-       message="Avoid really long Oracle object specifications and bodies ({0} lines found)."
-       class="net.sourceforge.pmd.lang.plsql.rule.codesize.ExcessiveObjectLengthRule"
-          externalInfoUrl="${pmd.website.baseurl}/rules/plsql/codesize.html#ExcessiveObjectLength">
-   <description>
+  <rule name="ExcessiveObjectLength"
+        language="plsql"
+        since="5.1"
+        message="Avoid really long Oracle object specifications and bodies ({0} lines found)."
+        class="net.sourceforge.pmd.lang.plsql.rule.codesize.ExcessiveObjectLengthRule"
+        externalInfoUrl="${pmd.website.baseurl}/pmd_rules_plsql_codesize.html#excessiveobjectlength">
+    <description>
 Excessive object line lengths are usually indications that the object may be burdened with excessive 
 responsibilities that could be provided by other objects. In breaking these methods
 apart the code becomes more managable and ripe for reuse.
-   </description>
-     <priority>3</priority>
-   <example>
+    </description>
+    <priority>3</priority>
+    <example>
 <![CDATA[
 CREATE OR REPLACE
 PACKAGE BODY Foo AS
-	PROCEDURE bar1 IS BEGIN
+    PROCEDURE bar1 IS BEGIN
     -- 1000 lines of code
-	END bar1;
-	PROCEDURE bar2 IS BEGIN
+    END bar1;
+    PROCEDURE bar2 IS BEGIN
     -- 1000 lines of code
-	END bar2;
+    END bar2;
     PROCEDURE bar3 IS BEGIN
     -- 1000 lines of code
-	END bar3;
-	
-	
+    END bar3;
+
+
     PROCEDURE barN IS BEGIN
     -- 1000 lines of code
-	END barn;
+    END barn;
 END;
 ]]>
-   </example>
- </rule>
+    </example>
+  </rule>
 
 
- <rule name="ExcessiveTypeLength"
-      language="plsql"
- 		 since="5.1"
-       message="Avoid really long Object Type specifications ({0} lines found)."
-       class="net.sourceforge.pmd.lang.plsql.rule.codesize.ExcessiveTypeLengthRule"
-          externalInfoUrl="${pmd.website.baseurl}/rules/plsql/codesize.html#ExcessiveTypeLength">
-   <description>
+  <rule name="ExcessiveTypeLength"
+        language="plsql"
+        since="5.1"
+        message="Avoid really long Object Type specifications ({0} lines found)."
+        class="net.sourceforge.pmd.lang.plsql.rule.codesize.ExcessiveTypeLengthRule"
+        externalInfoUrl="${pmd.website.baseurl}/pmd_rules_plsql_codesize.html#excessivetypelength">
+    <description>
 Excessive class file lengths are usually indications that the class may be burdened with excessive 
 responsibilities that could be provided by external classes or functions. In breaking these methods
 apart the code becomes more managable and ripe for reuse.
-   </description>
-     <priority>3</priority>
-   <example>
+    </description>
+    <priority>3</priority>
+    <example>
 <![CDATA[
 CREATE OR REPLACE
 TYPE BODY Foo AS
-	 MEMBER PROCEDURE bar1 IS BEGIN
+    MEMBER PROCEDURE bar1 IS BEGIN
     -- 1000 lines of code
-	END bar1;
-	 MEMBER PROCEDURE bar2 IS BEGIN
+    END bar1;
+    MEMBER PROCEDURE bar2 IS BEGIN
     -- 1000 lines of code
-	END bar2;
-     MEMBER PROCEDURE bar3 IS BEGIN
+    END bar2;
+    MEMBER PROCEDURE bar3 IS BEGIN
     -- 1000 lines of code
-	END bar3;
-	
-	
-     MEMBER PROCEDURE barN IS BEGIN
+    END bar3;
+
+
+    MEMBER PROCEDURE barN IS BEGIN
     -- 1000 lines of code
-	END barn;
+    END barn;
 END;
 ]]>
-   </example>
- </rule>
+    </example>
+  </rule>
 
- <rule name="ExcessivePackageBodyLength"
-      language="plsql"
- 		 since="5.1"
-       message="Avoid really long Object Type and Package bodies ({0} lines found)."
-       class="net.sourceforge.pmd.lang.plsql.rule.codesize.ExcessivePackageBodyLengthRule"
-          externalInfoUrl="${pmd.website.baseurl}/rules/plsql/codesize.html#ExcessivePackageBodyLength">
-   <description>
+  <rule name="ExcessivePackageBodyLength"
+        language="plsql"
+        since="5.1"
+        message="Avoid really long Object Type and Package bodies ({0} lines found)."
+        class="net.sourceforge.pmd.lang.plsql.rule.codesize.ExcessivePackageBodyLengthRule"
+        externalInfoUrl="${pmd.website.baseurl}/pmd_rules_plsql_codesize.html#excessivepackagebodylength">
+    <description>
 Excessive class file lengths are usually indications that the class may be burdened with excessive 
 responsibilities that could be provided by external classes or functions. In breaking these methods
 apart the code becomes more managable and ripe for reuse.
-   </description>
-     <priority>3</priority>
-   <example>
+    </description>
+    <priority>3</priority>
+    <example>
 <![CDATA[
 CREATE OR REPLACE
 PACKAGE BODY Foo AS
-	PROCEDURE bar1 IS BEGIN
+    PROCEDURE bar1 IS BEGIN
     -- 1000 lines of code
-	END bar1;
-	PROCEDURE bar2 IS BEGIN
+    END bar1;
+    PROCEDURE bar2 IS BEGIN
     -- 1000 lines of code
-	END bar2;
+    END bar2;
     PROCEDURE bar3 IS BEGIN
     -- 1000 lines of code
-	END bar3;
-	
-	
+    END bar3;
+
+
     PROCEDURE barN IS BEGIN
     -- 1000 lines of code
-	END barn;
+    END barn;
 END;
 ]]>
-   </example>
- </rule>
+    </example>
+  </rule>
 
 
- <rule name="ExcessivePackageSpecificationLength"
-      language="plsql"
- 		 since="5.1"
-		 message="Avoid really long Package Specifications ({0} lines found)."
-       class="net.sourceforge.pmd.lang.plsql.rule.codesize.ExcessivePackageSpecificationLengthRule"
-          externalInfoUrl="${pmd.website.baseurl}/rules/plsql/codesize.html#ExcessivePackageSpecificationLength">
-   <description>
+  <rule name="ExcessivePackageSpecificationLength"
+        language="plsql"
+        since="5.1"
+        message="Avoid really long Package Specifications ({0} lines found)."
+        class="net.sourceforge.pmd.lang.plsql.rule.codesize.ExcessivePackageSpecificationLengthRule"
+        externalInfoUrl="${pmd.website.baseurl}/pmd_rules_plsql_codesize.html#excessivepackagespecificationlength">
+    <description>
 Excessive class file lengths are usually indications that the class may be burdened with excessive 
 responsibilities that could be provided by external classes or functions. In breaking these methods
 apart the code becomes more managable and ripe for reuse.
-   </description>
-     <priority>3</priority>
-   <example>
+    </description>
+    <priority>3</priority>
+    <example>
 <![CDATA[
-]]>
 CREATE OR REPLACE
 PACKAGE Foo AS
-	PROCEDURE bar1 ;
-	PROCEDURE bar2 ;
-        PROCEDURE bar3 ;
-	
-    ..
-	
-        PROCEDURE barN ;
-END;
-   </example>
- </rule>
+    PROCEDURE bar1;
+    PROCEDURE bar2;
+    PROCEDURE bar3;
 
-    <rule 	name="CyclomaticComplexity"
-      language="plsql"
-    			since="5.1"
-      		message = "The {0} ''{1}'' has a Cyclomatic Complexity of {2}."
-	      	class="net.sourceforge.pmd.lang.plsql.rule.codesize.CyclomaticComplexityRule"
-	      	externalInfoUrl="${pmd.website.baseurl}/rules/plsql/codesize.html#CyclomaticComplexity">
-   <description>
-   		<![CDATA[
+    ...
+
+    PROCEDURE barN;
+END;
+]]>
+    </example>
+  </rule>
+
+  <rule name="CyclomaticComplexity"
+        language="plsql"
+        since="5.1"
+        message = "The {0} ''{1}'' has a Cyclomatic Complexity of {2}."
+        class="net.sourceforge.pmd.lang.plsql.rule.codesize.CyclomaticComplexityRule"
+        externalInfoUrl="${pmd.website.baseurl}/pmd_rules_plsql_codesize.html#cyclomaticcomplexity">
+    <description>
 Complexity directly affects maintenance costs is determined by the number of decision points in a method 
 plus one for the method entry.  The decision points include 'if', 'while', 'for', and 'case labels' calls.  
 Generally, numbers ranging from 1-4 denote low complexity, 5-7 denote moderate complexity, 8-10 denote
 high complexity, and 11+ is very high complexity.
-		]]>
-   </description>
-   <priority>3</priority>
-   <example>
+    </description>
+    <priority>3</priority>
+    <example>
 <![CDATA[
 -- Cyclomatic Complexity of 25 
-CREATE OR REPLACE PACKAGE BODY pkg_pmd_working_sequence  AS 
+CREATE OR REPLACE PACKAGE BODY pkg_pmd_working_sequence  AS
 1 PROCEDURE ty_logger  IS BEGIN
 2        IF true
          THEN
-              DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);         
-3		 IF true
-		 THEN
-		      DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);         
-4			 IF true
-			 THEN
-			      DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);         
-5			 ELSIF false
-			 THEN
-				DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-			 ELSE
-				DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-			 END IF;
-6		 ELSIF false
-		 THEN
-			DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-7			 IF true
-			 THEN
-			      DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);         
-8			 ELSIF false
-			 THEN
-				DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-			 ELSE
-				DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-			 END IF;
-		 ELSE
-			DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-9			 IF true
-			 THEN
-			      DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);         
-10			 ELSIF false
-			 THEN
-				DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-			 ELSE
-				DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-			 END IF;
-		 END IF;
+              DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);
+3        IF true
+         THEN
+              DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);
+4            IF true
+             THEN
+                  DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);
+5            ELSIF false
+             THEN
+                DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+             ELSE
+                DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+             END IF;
+6        ELSIF false
+         THEN
+            DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+7            IF true
+             THEN
+                  DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);
+8            ELSIF false
+             THEN
+                DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+             ELSE
+                DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+             END IF;
+         ELSE
+            DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+9            IF true
+             THEN
+                  DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);
+10           ELSIF false
+             THEN
+                DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+             ELSE
+                DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+             END IF;
+         END IF;
 11         ELSIF false
          THEN
-		DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-12		 IF true
-		 THEN
-		      DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);         
-13			 IF true
-			 THEN
-			      DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);         
-14			 ELSIF false
-			 THEN
-				DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-			 ELSE
-				DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-			 END IF;
-15		 ELSIF false
-		 THEN
-16			 IF true
-			 THEN
-			      DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);         
-17			 ELSIF false
-			 THEN
-				DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-			 ELSE
-				DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-			 END IF;
-			DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-		 ELSE
-			DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-		 END IF;
-	 ELSE
-		DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-18		 IF true
-		 THEN
-		      DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);         
-19			 IF true
-			 THEN
-			      DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);         
-20			 ELSIF false
-			 THEN
-				DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-			 ELSE
-				DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-			 END IF;
-21		 ELSIF false
-		 THEN
-			DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-22			 IF true
-			 THEN
-			      DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);         
-23			 ELSIF false
-			 THEN
-				DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-			 ELSE
-				DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-			 END IF;
-		 ELSE
-			DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-24			 IF true
-			 THEN
-			      DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);         
-25			 ELSIF false
-			 THEN
-				DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-			 ELSE
-				DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);             
-			 END IF;
-		 END IF;
-	 END IF;
-END;								
-						
+            DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+12       IF true
+         THEN
+              DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);
+13           IF true
+             THEN
+                  DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);
+14           ELSIF false
+             THEN
+                DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+             ELSE
+                DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+             END IF;
+15       ELSIF false
+         THEN
+16           IF true
+             THEN
+                  DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);
+17           ELSIF false
+             THEN
+                DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+             ELSE
+                DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+             END IF;
+             DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+         ELSE
+             DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+         END IF;
+     ELSE
+        DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+18       IF true
+         THEN
+              DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);
+19           IF true
+             THEN
+                  DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);
+20           ELSIF false
+             THEN
+                DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+             ELSE
+                DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+             END IF;
+21       ELSIF false
+         THEN
+            DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+22           IF true
+             THEN
+                DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);
+23           ELSIF false
+             THEN
+                DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+             ELSE
+                DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+             END IF;
+             ELSE
+             DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+24           IF true
+             THEN
+                  DBMS_OUTPUT.PUT_LINE('IF/THEN l_Integer='||l_integer);
+25           ELSIF false
+             THEN
+                DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+             ELSE
+                DBMS_OUTPUT.PUT_LINE('ELSIF l_Integer='||l_integer);
+             END IF;
+         END IF;
+     END IF;
+END;
+
 END;
 ]]>
-   </example>
-</rule>
+    </example>
+  </rule>
 
 
 <!--
-    <rule name="ExcessivePublicCount"
-      language="plsql"
-    since="5.1"
-    message="This class has a bunch of public methods and attributes"
-    class="net.sourceforge.pmd.lang.plsql.rule.codesize.ExcessivePublicCountRule"
-          externalInfoUrl="${pmd.website.baseurl}/rules/plsql/codesize.html#ExcessivePublicCount">
+  <rule name="ExcessivePublicCount"
+        language="plsql"
+        since="5.1"
+        message="This class has a bunch of public methods and attributes"
+        class="net.sourceforge.pmd.lang.plsql.rule.codesize.ExcessivePublicCountRule"
+        externalInfoUrl="${pmd.website.baseurl}/pmd_rules_plsql_codesize.html#excessivepubliccount">
     <description>
 Classes with large numbers of public methods and attributes require disproportionate testing efforts
 since combinational side effects grow rapidly and increase risk. Refactoring these classes into
@@ -404,61 +397,60 @@ developed easily.
     </description>
     <priority>3</priority>
     <example>
-    <![CDATA[
+<![CDATA[
 public class Foo {
-	public String value;
-	public Bar something;
-	public Variable var;
- // [... more more public attributes ...]
- 
-	public void doWork() {}
-	public void doMoreWork() {}
-	public void doWorkAgain() {}
- // [... more more public methods ...]
+    public String value;
+    public Bar something;
+    public Variable var;
+// [... more more public attributes ...]
+
+    public void doWork() {}
+    public void doMoreWork() {}
+    public void doWorkAgain() {}
+// [... more more public methods ...]
 }
-    ]]>
+]]>
     </example>
-    </rule>
+  </rule>
 -->
 
-    <rule name="TooManyFields"
-      language="plsql"
-    		 since="5.1"
-		 message="Too many fields"
-          class="net.sourceforge.pmd.lang.plsql.rule.codesize.TooManyFieldsRule"
-          externalInfoUrl="${pmd.website.baseurl}/rules/plsql/codesize.html#TooManyFields">
-      <description>
+  <rule name="TooManyFields"
+        language="plsql"
+        since="5.1"
+        message="Too many fields"
+        class="net.sourceforge.pmd.lang.plsql.rule.codesize.TooManyFieldsRule"
+        externalInfoUrl="${pmd.website.baseurl}/pmd_rules_plsql_codesize.html#toomanyfields">
+    <description>
 Classes that have too many fields can become unwieldy and could be redesigned to have fewer fields,
 possibly through grouping related fields in new objects.  For example, a class with individual 
 city/state/zip fields could park them within a single Address field.
-      </description>
-        <priority>3</priority>
-      <example>
-   <![CDATA[
+    </description>
+    <priority>3</priority>
+    <example>
+<![CDATA[
 CREATE OR REPLACE PACKAGE pkg_too_many_fields AS
     C_CHAR_A CONSTANT CHAR(1 CHAR) := 'A';
     C_CHAR_B CONSTANT CHAR(1 CHAR) := 'B';
     ...
     C_CHAR_Z CONSTANT CHAR(1 CHAR) := 'Z';
 END pkg_too_many_fields;
+]]>
+    </example>
+  </rule>
 
-   ]]>
-      </example>
-    </rule>
-
-
-<rule name="NcssMethodCount" message="The method {0}() has an NCSS line count of {1}"
-      language="plsql"
-   since="5.1"
-   class="net.sourceforge.pmd.lang.plsql.rule.codesize.NcssMethodCountRule"
-   externalInfoUrl="${pmd.website.baseurl}/rules/plsql/codesize.html#NcssMethodCount">
+  <rule name="NcssMethodCount"
+        message="The method {0}() has an NCSS line count of {1}"
+        language="plsql"
+        since="5.1"
+        class="net.sourceforge.pmd.lang.plsql.rule.codesize.NcssMethodCountRule"
+        externalInfoUrl="${pmd.website.baseurl}/pmd_rules_plsql_codesize.html#ncssmethodcount">
     <description>
 This rule uses the NCSS (Non-Commenting Source Statements) algorithm to determine the number of lines
 of code for a given method. NCSS ignores comments, and counts actual statements. Using this algorithm,
 lines of code that are split are counted as one.
     </description>
     <priority>3</priority>
-   <example>
+    <example>
 <![CDATA[
 CREATE OR REPLACE PACKAGE BODY AS
  FUNCTION methd RETURN INTEGER IS
@@ -467,21 +459,22 @@ CREATE OR REPLACE PACKAGE BODY AS
  END;
 END;
 ]]>
-   </example>
-</rule>
+    </example>
+  </rule>
 
-<rule name="NcssObjectCount" message="The Oracle object has an NCSS line count of {0}"
-      language="plsql"
-   since="5.1"
-   class="net.sourceforge.pmd.lang.plsql.rule.codesize.NcssObjectCountRule"
-   externalInfoUrl="${pmd.website.baseurl}/rules/plsql/codesize.html#NcssObjectCount">
+  <rule name="NcssObjectCount"
+        message="The Oracle object has an NCSS line count of {0}"
+        language="plsql"
+        since="5.1"
+        class="net.sourceforge.pmd.lang.plsql.rule.codesize.NcssObjectCountRule"
+        externalInfoUrl="${pmd.website.baseurl}/pmd_rules_plsql_codesize.html#ncssobjectcount">
     <description>
 This rule uses the NCSS (Non-Commenting Source Statements) algorithm to determine the number of lines
 of code for a given Oracle object. NCSS ignores comments, and counts actual statements. Using this algorithm,
 lines of code that are split are counted as one.
     </description>
     <priority>3</priority>
-   <example>
+    <example>
 <![CDATA[
 CREATE OR REPLACE PACKAGE pkg_
  PROCEDURE Foo IS
@@ -492,27 +485,25 @@ CREATE OR REPLACE PACKAGE pkg_
  END;
 }
 ]]>
-   </example></rule>
+    </example>
+  </rule>
 
-    <rule
-      language="plsql"
+  <rule language="plsql"
         name="TooManyMethods"
         since="5.1"
         class="net.sourceforge.pmd.lang.rule.XPathRule"
         message="This object has too many methods, consider refactoring it."
-        externalInfoUrl="${pmd.website.baseurl}/rules/plsql/codesize.html#TooManyMethods">
-        <description>
-            <![CDATA[
+        externalInfoUrl="${pmd.website.baseurl}/pmd_rules_plsql_codesize.html#toomanymethods">
+    <description>
 A package or type with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to
 have more fine grained objects.
-            ]]>
-        </description>
-        <priority>3</priority>
-        <properties>
-                <property name="maxmethods" type="Integer" description="The method count reporting threshold" min="1" max="1000" value="1"/>
-                <property name="xpath">
-                <value>
-                    <![CDATA[
+    </description>
+    <priority>3</priority>
+    <properties>
+        <property name="maxmethods" type="Integer" description="The method count reporting threshold" min="1" max="1000" value="1"/>
+        <property name="xpath">
+            <value>
+<![CDATA[
 //node()
      [ (
         local-name(.) = 'PackageSpecification'
@@ -544,10 +535,10 @@ have more fine grained objects.
            )
       ) > $maxmethods
      ]
-                    ]]>
-                </value>
-            </property>
-        </properties>
-    </rule>
+]]>
+            </value>
+        </property>
+    </properties>
+  </rule>
 
 </ruleset>
diff --git a/pmd-plsql/src/main/resources/rulesets/plsql/dates.xml b/pmd-plsql/src/main/resources/rulesets/plsql/dates.xml
index 41eefbf2d2..70339133d2 100644
--- a/pmd-plsql/src/main/resources/rulesets/plsql/dates.xml
+++ b/pmd-plsql/src/main/resources/rulesets/plsql/dates.xml
@@ -8,149 +8,150 @@
 The Dates ruleset deals with PLSQL DATETIME usages.
   </description>
 
-<rule name="TO_DATEWithoutDateFormat"
-      language="plsql"
-      since="5.1"
-      message="TO_DATE without date format"
-      class="net.sourceforge.pmd.lang.rule.XPathRule"
-      externalInfoUrl="${pmd.website.baseurl}/rules/plsql/dates.html#TO_DATEWithoutDateFormat">
-  <description>
-  TO_DATE without date format- use TO_DATE(expression, date-format)
-  </description>
-  <priority>3</priority>
-  <properties>
-    <property name="xpath">
-    <value>
+  <rule name="TO_DATEWithoutDateFormat"
+        language="plsql"
+        since="5.1"
+        message="TO_DATE without date format"
+        class="net.sourceforge.pmd.lang.rule.XPathRule"
+        externalInfoUrl="${pmd.website.baseurl}/pmd_rules_plsql_dates.html#to_datewithoutdateformat">
+    <description>
+TO_DATE without date format- use TO_DATE(expression, date-format)
+    </description>
+    <priority>3</priority>
+    <properties>
+        <property name="xpath">
+            <value>
 <![CDATA[
-//PrimaryExpression[PrimaryPrefix/Name/@Image='TO_DATE'  and count(PrimarySuffix/Arguments/ArgumentList/Argument) = 1 ] 
+//PrimaryExpression[PrimaryPrefix/Name/@Image='TO_DATE'  and count(PrimarySuffix/Arguments/ArgumentList/Argument) = 1 ]
 ]]>
-    </value>
-    </property>
-  </properties>
-  <example>
+            </value>
+        </property>
+    </properties>
+    <example>
 <![CDATA[
 CREATE OR REPLACE PACKAGE BODY date_utilities
 IS
- 
--- Take single parameter, relyimg on current default NLS date format 
+
+-- Take single parameter, relyimg on current default NLS date format
 FUNCTION to_date_single_parameter (p_date_string IN VARCHAR2) RETURN DATE
 IS
 BEGIN
-   RETURN TO_DATE(p_date_string); 
+   RETURN TO_DATE(p_date_string);
 END to_date_single_parameter ;
 
--- Take 2 parameters, using an explicit date format string  
+-- Take 2 parameters, using an explicit date format string
 FUNCTION to_date_two_parameters (p_date_string IN VARCHAR2, p_format_mask IN VARCHAR2) RETURN DATE
 IS
 BEGIN
-   TO_DATE(p_date_string, p_date_format); 
-END to_date_two_parameters ;
+   TO_DATE(p_date_string, p_date_format);
+END to_date_two_parameters;
 
--- Take 3 parameters, using an explicit date format string and an explicit language    
+-- Take 3 parameters, using an explicit date format string and an explicit language
 FUNCTION to_date_three_parameters (p_date_string IN VARCHAR2, p_format_mask IN VARCHAR2, p_nls_language VARCHAR2 ) RETURN DATE
 IS
 BEGIN
-   TO_DATE(p_date_string, p_format_mask, p_nls_language); 
-END to_date_three_parameters ;
+   TO_DATE(p_date_string, p_format_mask, p_nls_language);
+END to_date_three_parameters;
 
-END date_utilities ;
+END date_utilities;
 /
 ]]>
-  </example>
-</rule>
+    </example>
+  </rule>
 
-<rule name="TO_DATE_TO_CHAR"
-      language="plsql"
-      since="5.1"
-      message="TO_DATE(TO_CHAR(variable)) instead of TRUNC(variable)"
-      class="net.sourceforge.pmd.lang.rule.XPathRule"
-      externalInfoUrl="${pmd.website.baseurl}/rules/plsql/dates.html#TO_DATE_TO_CHAR">
-  <description>
-  TO_DATE(TO_CHAR(date-variable)) used to remove time component - use TRUNC(date-veriable)
-  </description>
-  <priority>3</priority>
-  <properties>
-    <property name="xpath">
-    <value>
+  <rule name="TO_DATE_TO_CHAR"
+        language="plsql"
+        since="5.1"
+        message="TO_DATE(TO_CHAR(variable)) instead of TRUNC(variable)"
+        class="net.sourceforge.pmd.lang.rule.XPathRule"
+        externalInfoUrl="${pmd.website.baseurl}/pmd_rules_plsql_dates.html#to_date_to_char">
+    <description>
+TO_DATE(TO_CHAR(date-variable)) used to remove time component - use TRUNC(date-veriable)
+    </description>
+    <priority>3</priority>
+    <properties>
+        <property name="xpath">
+            <value>
 <![CDATA[
-//PrimaryExpression[PrimaryPrefix/Name/@Image='TO_DATE' 
-                             and count(PrimarySuffix/Arguments/ArgumentList/Argument) = 1 
-                                                         and .//PrimaryExpression[PrimaryPrefix/Name/@Image='TO_CHAR'  
-                                                                                  and count(PrimarySuffix/Arguments/ArgumentList/Argument) = 1 
-                                                                                 ] 
-                   ] 
+//PrimaryExpression
+    [PrimaryPrefix/Name/@Image='TO_DATE']
+    [count(PrimarySuffix/Arguments/ArgumentList/Argument) = 1]
+    [.//PrimaryExpression
+        [PrimaryPrefix/Name/@Image='TO_CHAR']
+        [count(PrimarySuffix/Arguments/ArgumentList/Argument) = 1]
+    ]
 ]]>
-    </value>
-    </property>
-  </properties>
-  <example>
+            </value>
+        </property>
+    </properties>
+    <example>
 <![CDATA[
 CREATE OR REPLACE PACKAGE BODY date_utilities
 IS
  
--- Take single parameter, relyimg on current default NLS date format 
+-- Take single parameter, relyimg on current default NLS date format
 FUNCTION strip_time (p_date IN DATE) RETURN DATE
 IS
 BEGIN
-   RETURN TO_DATE(TO_CHAR(p_date)); 
-END strip_time ;
+   RETURN TO_DATE(TO_CHAR(p_date));
+END strip_time;
 
 
-END date_utilities ;
+END date_utilities;
 /
 ]]>
-  </example>
-</rule>
+    </example>
+  </rule>
 
-<rule name="TO_TIMESTAMPWithoutDateFormat"
-      language="plsql"
-      message="TO_TIMESTAMP without date format"
-      class="net.sourceforge.pmd.lang.rule.XPathRule"
-      since="5.1"
-      externalInfoUrl="${pmd.website.baseurl}/rules/plsql/dates.html#TO_TIMESTAMPWithoutDateFormat">
-  <description>
-  TO_TIMESTAMP without date format- use TO_TIMESTAMP(expression, date-format)
-  </description>
-  <priority>3</priority>
-  <properties>
-    <property name="xpath">
-    <value>
+  <rule name="TO_TIMESTAMPWithoutDateFormat"
+        language="plsql"
+        message="TO_TIMESTAMP without date format"
+        class="net.sourceforge.pmd.lang.rule.XPathRule"
+        since="5.1"
+        externalInfoUrl="${pmd.website.baseurl}/pmd_rules_plsql_dates.html#to_timestampwithoutdateformat">
+    <description>
+TO_TIMESTAMP without date format- use TO_TIMESTAMP(expression, date-format)
+    </description>
+    <priority>3</priority>
+    <properties>
+        <property name="xpath">
+            <value>
 <![CDATA[
 //PrimaryExpression[PrimaryPrefix/Name/@Image='TO_TIMESTAMP'  and count(PrimarySuffix/Arguments/ArgumentList/Argument) = 1 ] 
 ]]>
-    </value>
-    </property>
-  </properties>
-  <example>
+            </value>
+        </property>
+    </properties>
+    <example>
 <![CDATA[
 CREATE OR REPLACE PACKAGE BODY date_utilities
 IS
- 
--- Take single parameter, relyimg on current default NLS date format 
+
+-- Take single parameter, relyimg on current default NLS date format
 FUNCTION to_timestamp_single_parameter (p_date_string IN VARCHAR2) RETURN DATE
 IS
 BEGIN
-   RETURN TO_TIMESTAMP(p_date_string); 
-END to_timestamp_single_parameter ;
+   RETURN TO_TIMESTAMP(p_date_string);
+END to_timestamp_single_parameter;
 
--- Take 2 parameters, using an explicit date format string  
+-- Take 2 parameters, using an explicit date format string
 FUNCTION to_timestamp_two_parameters (p_date_string IN VARCHAR2, p_format_mask IN VARCHAR2) RETURN DATE
 IS
 BEGIN
-   TO_TIMESTAMP(p_date_string, p_date_format); 
-END to_timestamp_two_parameters ;
+   TO_TIMESTAMP(p_date_string, p_date_format);
+END to_timestamp_two_parameters;
 
--- Take 3 parameters, using an explicit date format string and an explicit language    
+-- Take 3 parameters, using an explicit date format string and an explicit language
 FUNCTION to_timestamp_three_parameters (p_date_string IN VARCHAR2, p_format_mask IN VARCHAR2, p_nls_language VARCHAR2 ) RETURN DATE
 IS
 BEGIN
-   TO_TIMESTAMP(p_date_string, p_format_mask, p_nls_language); 
-END to_timestamp_three_parameters ;
+   TO_TIMESTAMP(p_date_string, p_format_mask, p_nls_language);
+END to_timestamp_three_parameters;
 
-END date_utilities ;
+END date_utilities;
 /
 ]]>
-  </example>
-</rule>
-</ruleset>
+    </example>
+  </rule>
 
+</ruleset>
diff --git a/pmd-plsql/src/main/resources/rulesets/plsql/rulesets.properties b/pmd-plsql/src/main/resources/rulesets/plsql/rulesets.properties
index ae519eb457..018e4b3912 100644
--- a/pmd-plsql/src/main/resources/rulesets/plsql/rulesets.properties
+++ b/pmd-plsql/src/main/resources/rulesets/plsql/rulesets.properties
@@ -2,4 +2,8 @@
 # BSD-style license; for more info see http://pmd.sourceforge.net/license.html
 #
 
-rulesets.filenames=rulesets/plsql/codesize.xml,rulesets/plsql/dates.xml,rulesets/plsql/TomKytesDespair.xml,rulesets/plsql/strictsyntax.xml
+rulesets.filenames=\
+    rulesets/plsql/codesize.xml,\
+    rulesets/plsql/dates.xml,\
+    rulesets/plsql/TomKytesDespair.xml,\
+    rulesets/plsql/strictsyntax.xml
diff --git a/pmd-plsql/src/main/resources/rulesets/plsql/strictsyntax.xml b/pmd-plsql/src/main/resources/rulesets/plsql/strictsyntax.xml
index 5d88e3c523..c8f8d32265 100644
--- a/pmd-plsql/src/main/resources/rulesets/plsql/strictsyntax.xml
+++ b/pmd-plsql/src/main/resources/rulesets/plsql/strictsyntax.xml
@@ -8,12 +8,12 @@
 The Strict Syntax ruleset contains rules that highlight invalid plsql syntax, which works, but should be avoided.
   </description>
 
-<rule name="MisplacedPragma"
-      language="plsql"
-      since="5.5.2"
-      message="Pragma should be used only inside the declaration block before 'BEGIN'."
-      class="net.sourceforge.pmd.lang.rule.XPathRule"
-      externalInfoUrl="${pmd.website.baseurl}/rules/plsql/strictsyntax.html#MisplacedPragma">
+  <rule name="MisplacedPragma"
+        language="plsql"
+        since="5.5.2"
+        message="Pragma should be used only inside the declaration block before 'BEGIN'."
+        class="net.sourceforge.pmd.lang.rule.XPathRule"
+        externalInfoUrl="${pmd.website.baseurl}/pmd_rules_plsql_strictsyntax.html#misplacedpragma">
     <description>
 Oracle states that the PRAQMA AUTONOMOUS_TRANSACTION must be in the declaration block,
 but the code does not complain, when being compiled on the 11g DB.
@@ -22,12 +22,15 @@ https://docs.oracle.com/cd/B28359_01/appdev.111/b28370/static.htm#BABIIHBJ
     <priority>3</priority>
     <properties>
         <property name="xpath">
-            <value><![CDATA[
+            <value>
+<![CDATA[
 //ProgramUnit/Pragma
-            ]]></value>
+]]>
+            </value>
         </property>
     </properties>
-    <example><![CDATA[
+    <example>
+<![CDATA[
 create or replace package inline_pragma_error is
 
 end;
@@ -44,8 +47,8 @@ create or replace package body inline_pragma_error is
 
 end inline_pragma_error;
 /
-
-    ]]></example>
-</rule>
+]]>
+    </example>
+  </rule>
 
 </ruleset>