FlexPMD

FlexPMD uses a part of PMD, its Java well known counterpart.

Overview

FlexPMD is a tool that helps to improve code quality by auditing any AS3/Flex source directory and detecting common bad practices, such as:

• Unused code (functions, variables, constants, etc.)
• Inefficient code (misuse of dynamic filters, heavy constructors, etc.)
• Over-complex code (nested loops, too many conditionals, etc.)
• Over-long code (classes, methods, etc.)
• Incorrect use of the Flex component lifecycle (commitProperties, etc.)

A report is produced describing the violations of a given rule set. FlexPMD includes a rule set that is broad ranging and continually growing. It is also straightforward to create new rules and users are encouraged to do so.

FlexPMD can currently be invoked from:

• The command line
• Maven
• Ant
• Automator on Mac OS X
• Eclipse new
• TextMate on Mac OS X new
• FlashDevelop new

Currently, FlexPMD produces a XML report by default, plus an HTML report when invoked by the Maven site plugin. The XML report can then be consumed by any PMD reports pretty printers (like the PMD hudson plugin).

An Eclipse plugin is under development.

Here is the kind of report you can have as an output of FlexPMD (violations in given file):

and a trend of the violation:

Download

Visit the Downloads page to view the downloads available.

Known issues/limitations

Known issues Stack traces can be thrown during parsing. They are caught though during analyzing the code base, and hence fails over

Getting Involved

There are many ways to contribute to FlexPMD:

• Ask and answer questions on the forums and mailing lists
  
• Investigate bugs that have been filed and contribute patches where appropriate
• Request a feature
  
• Contribute to the developer documentation

‍ More information