[
http://jira.codehaus.org/browse/MPMD-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133204#action_133204
]
Ulli Hafner commented on MPMD-73:
---------------------------------
This problem is especially annoying if you use individual rulesets for each
maven "leaf" module: for findbugs and checkstyle (and PMD) we define in the
root pom the config file with ${project.artifactId}/configuration.xml. For pmd
this does not work because of this bug. The pmd module always wants to read the
configuration for our parent modules that do not contain source (just a modules
section in the pom). So we need to create a dummy file for each of our parent
modules just to prevent pmd from reporting a build failure.
> Report generated even when no input files present
> -------------------------------------------------
>
> Key: MPMD-73
> URL: http://jira.codehaus.org/browse/MPMD-73
> Project: Maven 2.x PMD Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Reporter: Simon Kitching
> Priority: Minor
>
> Most maven report plugins will not generate a report if there are no input
> files. For example, a pom that defines the javadoc report plugin but has no
> source does not get a javadoc report.
> However the pmd plugin generates empty pmd and cmd reports even for projects
> that have no source. In particular this means that parent poms that want to
> define pmd reports for the child modules get a "project reports" menu with
> pointless pmd/cmd pages. Given that poms lack a "pluginManagement" pom
> section, this is quite annoying.
--
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
