You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Daniel Kulp <dk...@apache.org> on 2008/05/29 17:15:19 UTC

[ANN] Maven PMD Plugin 2.4 released

The Maven team is pleased to announce the release of the Maven PMD  
Plugin, version 2.4

This plugin is used to check java sources for potential programming  
problems like possible bugs, dead code, suboptimal code, etc...

  http://maven.apache.org/plugins/maven-pmd-plugin/

You can specify the plugin version in your project's plugin  
configuration:
<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-pmd-plugin</artifactId>
    <version>2.4</version>
</plugin>


This release includes several bug fixes and other improvements:

** Bug
  * [MPMD-61] - When running build using "-f <path_to_pom>/pom.xml"  
the site is stored in working directory instead of project directory
  * [MPMD-70] - Move hard-coded strings to resource bundle
  * [MPMD-75] - PMD plugin unable to exclude groovy-stub files.
  * [MPMD-77] - excludeRoots doesn't work with basedir-relative paths

** Improvement
  * [MPMD-64] - verbose output not useful for inner classes
  * [MPMD-71] - Add german translation
  * [MPMD-72] - Add dedicated resource bundles for locale "en"
  * [MPMD-74] - Clarify usage of outputDirectory parameter
  * [MPMD-76] - use ${project.build.sourceEncoding} as default value  
for "sourceEncoding" parameter
  * [MPMD-79] - Warn about usage of platform encoding

** Task
  * [MPMD-78] - Update to PMD 4.2.1   (actually to 4.2.2)


---
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog