##### Overview

- Download PMD 5.0.5
- What's new in PMD 5.0.5
- PMD in the news
- PMD-related products and books
- Best practices
- Future directions
- Similar projects
- Credits
- License
- What does 'PMD' mean?

##### Usage

- Installation
- Command line usage
- Ant task usage
- Maven plugin usage
- Mvn plugin usage
- IDE plugin usage
- Suppressing warnings
- Finding duplicated code
- JSP support

##### Customizing PMD

- Compiling PMD
- How to write a rule
- Writing XPath rules
- How to make a rule set
- How it works
- Rule guidelines
- PMD developers information
- PMD Release Process

##### For example

- Run PMD on a Sourceforge project

##### Misc.

- XPath tutorial (Gregorian)

##### Rule Sets

- ecmascript
  - Basic Ecmascript
  - Braces
  - Unnecessary
- java
  - Android
  - Basic
  - Braces
  - Clone Implementation
  - Code Size
  - Comments
  - Controversial
  - Coupling
  - Design
  - Empty Code
  - Finalizer
  - Import Statements
  - J2EE
  - JavaBeans
  - JUnit
  - Jakarta Commons Logging
  - Java Logging
  - Migration
  - Naming
  - Optimization
  - Strict Exceptions
  - String and StringBuffer
  - Security Code Guidelines
  - Type Resolution
  - Unnecessary
  - Unused Code
- jsp
  - Basic JSF
  - Basic JSP
- xml
  - Basic XML
- xsl
  - XPath in XSL

##### Project Documentation

- Project Information
- Project Reports

## How to make a new rule set

Say you want to pick specific rules from various rule sets and customize them. You can do this by making your own rule set.

### Create a new ruleset.xml file

Use one of the current rulesets as an example. Copy and paste it into your new file, delete all the old rules from it, and change the name and description. Like this:

    <?xml version="1.0"?>
    <ruleset name="Custom ruleset"
        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>
      This ruleset checks my code for bad stuff
      </description>
    </ruleset>

### Add some rule references to it

After you add these references it'll look something like this:

    <?xml version="1.0"?>
    <ruleset name="Custom ruleset"
        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>
      This ruleset checks my code for bad stuff
      </description>

      <!-- We'll use the entire 'strings' ruleset -->
      <rule ref="rulesets/java/strings.xml"/>

      <!-- Here's some rules we'll specify one at a time -->
      <rule ref="rulesets/java/unusedcode.xml/UnusedLocalVariable"/>
      <rule ref="rulesets/java/unusedcode.xml/UnusedPrivateField"/>
      <rule ref="rulesets/java/imports.xml/DuplicateImports"/>
      <rule ref="rulesets/java/basic.xml/UnnecessaryConversionTemporary"/>

      <!-- We want to customize this rule a bit, change the message and raise the priority  -->
      <rule
       ref="rulesets/java/basic.xml/EmptyCatchBlock"
       message="Must handle exceptions">
        <priority>2</priority>
      </rule>

      <!-- Now we'll customize a rule's property value -->
      <rule ref="rulesets/java/codesize.xml/CyclomaticComplexity">
        <properties>
            <property name="reportLevel" value="5"/>
        </properties>
      </rule>

      <!-- We want everything from braces.xml except WhileLoopsMustUseBraces -->
      <rule ref="rulesets/java/braces.xml">
        <exclude name="WhileLoopsMustUseBraces"/>
      </rule>
    </ruleset>

Notice that you can customize individual referenced rules. Everything but the class of the rule can be overridden in your custom ruleset.

### Excluding rules from a ruleset

You can also make a custom ruleset that excludes rules, like this:

    <?xml version="1.0"?>
    <ruleset name="mybraces"
        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>Just the braces rules I like</description>
      <rule ref="rulesets/java/braces.xml">
        <exclude name="WhileLoopsMustUseBraces"/>
        <exclude name="IfElseStmtsMustUseBraces"/>
      </rule>
    </ruleset>

### Excluding files from a ruleset

You can also exclude certain files from being processed by a ruleset using exclude patterns, with an optional overriding include pattern. A file will be excluded from processing when there is a matching exclude pattern, but no matching include pattern. Path separators in the source file path are normalized to be the '/' character, so the same ruleset can be used on multiple platforms transparently. Additionally, this exclude/include technique works regardless of how PMD is used (e.g. command line, IDE, Ant), making it easier to keep application of your PMD rules consistent throughout your environment. Here is an example:

    <?xml version="1.0"?>
    <ruleset name="myruleset"
        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>My ruleset</description>
      <exclude-pattern>.*/some/package/.*</exclude-pattern>
      <exclude-pattern>.*/some/other/package/FunkyClassNamePrefix.*</exclude-pattern>
      <include-pattern>.*/some/package/ButNotThisClass.*</include-pattern>
      <rule>...
    </ruleset>

### Reference it in your Ant task

You can specify the full path to your custom ruleset name alongside of the built-in PMD rulesets - like this:

    <pmd rulesetfiles="/home/tom/data/pmd/pmd/rulesets/java/design.xml,rulesets/java/unusedcode.xml">
      <formatter type="xml" toFile="foo.xml"/>
      <fileset dir="/home/tom/data/pmd/pmd/src">
        <include name="**/*.java"/>
      </fileset>
    </pmd>

### To see it in your IDE, add it to rulesets/rulesets.properties

At least, that's the way some of the IDE plugins do it. Some have other ways of adding custom rulesets.

### Send us feedback

If you have suggestions on clarifying this document, please post them to the forum. Thanks!

Finally, for many more details on building custom rulesets, pick up PMD Applied!