[
http://jira.codehaus.org/browse/MPMD-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128772#action_128772
]
Xavier Le Vourch commented on MPMD-64:
--------------------------------------
The just released pmd 4.2 fixes this problem as the inner classes names are not
correctly generated in the xml reports.
Updating the pmd-jdk14 version required in pom.xml to 4.2 is all that's
needed...
Xavier
Index: pom.xml
===================================================================
--- pom.xml (revision 641455)
+++ pom.xml (working copy)
@@ -156,7 +156,7 @@
<dependency>
<groupId>pmd</groupId>
<artifactId>pmd-jdk14</artifactId>
- <version>4.1.1</version>
+ <version>4.2</version>
</dependency>
<!-- test -->
<dependency>
> verbose output not useful for inner classes
> -------------------------------------------
>
> Key: MPMD-64
> URL: http://jira.codehaus.org/browse/MPMD-64
> Project: Maven 2.x PMD Plugin
> Issue Type: Improvement
> Components: PMD
> Affects Versions: 2.2
> Reporter: Sean Bridges
> Priority: Minor
>
> With verbose output on, a pmd error in an inner class will produce output
> like,
> [INFO] PMD Failure: foo.bar.Anonymous$1:182
> Rule:SignatureDeclareThrowsException Priority:3 A method/constructor
> shouldn't explicitly throw java.lang.Exception.
> Rather than printing the class name, it would be more useful to print out the
> file name.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
