You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/02/10 20:49:18 UTC
[jira] [Commented] (MPMD-219) Maven PMD Plugin ignores PMD
processing errors
[ https://issues.apache.org/jira/browse/MPMD-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141527#comment-15141527 ]
ASF GitHub Bot commented on MPMD-219:
-------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/maven-plugins/pull/80
> Maven PMD Plugin ignores PMD processing errors
> ----------------------------------------------
>
> Key: MPMD-219
> URL: https://issues.apache.org/jira/browse/MPMD-219
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
> Affects Versions: 3.0
> Reporter: Andreas Dangel
> Assignee: Andreas Dangel
> Priority: Minor
> Fix For: 3.7
>
>
> If a source file cannot be parsed by PMD, the error is reported as a "processing error" and continues with the next file.
> However, the maven plugin doesn't use this information. This leads to a situation, where project build is successful despite PMD violations - because PMD skipped files which it can't parse.
> This is not such a big problem if the files are compiled before (e.g. executing PMD in a phase later than compile) - as the compiler plugin would fail the build already.
> But if "pmd:pmd" or "pmd:check" is called directly, maven would not fail the build.
> See also https://sourceforge.net/p/pmd/mailman/message/34715839/
> I'll provide a PR for this bug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)