Vincent Massol Emmanuel Venisse The links to source xref files does not honor maven.jxr.destdir and maven.jxr.destdir.test. RSS file has incorrect links when used in multiproject build. maven.checkstyle.header.file now defaults to ${maven.license.licenseFile}. ClassCastException when moving from 2.5 to 3.0. Use a jsl transform instead of ant's style task. Upgraded to checkstyle 4.1. Do not assert ASF copyright in checkstyle.rss. Added new summary report as front page. Moved reports under the checkstyle folder and renamed. Added maven.checkstyle.dir and move output files there. Added properties maven.checkstyle.output.xml and maven.checkstyle.output.txt The checkstyle plugin use the maven.xdoc.locale.default to generate the report. Ability to check test sources using property maven.checkstyle.check.tests Generate reports filtered by severity Support for Java5 Fixed MemberName rule in Turbine checkstyle rules Added new maven.checkstyle.suppressions.fileproperty. Added generation of a Checkstyle RSS feed. Fix : Build failed if target directory and License file didn't exist. Fix checks built into plugin when not run on Windows. Allow Checkstyle plugin to access checks file from a URL. Upgraded to Checkstyle 3.4. Applied MPCHECKSTYLE-15. Upgraded to Checkstyle 3.3. The Checkstyle HTML report now provides information on severity. Prevent projects who do not use the head check from failing if they don't provide a license file. Upgraded to Checkstyle 3.2. Added ignoreLines 1, 6. Update to use maven.docs.*/maven.gen.docs Add maven dependency and classes directory to classpath. This stops 'Unable to get class information for '<classname>' errors. Add xml declaration to generated report. Fixed for character encoding. I register reports only if source, test,... exists. So, corresponding entrys in menu will appear only if reports are registered. Upgraded to Checkstyle 3.1. Updated documentation. Complete clean of the existing plugin. Added a new maven.checkstyle.useFileproperty. If false, the checkstyle task will display violations on stdout. If true, a text file will be created with the violations. Note: this is in addition to the XML result file (containing the violations in XML format) which is always created.