You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2018/03/16 22:40:22 UTC
[jira] [Closed] (MPMD-132) Cannot configure multiple executions
(ie. cpd, pmd) independantly
[ https://issues.apache.org/jira/browse/MPMD-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MPMD-132.
-------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.
> Cannot configure multiple executions (ie. cpd, pmd) independantly
> -----------------------------------------------------------------
>
> Key: MPMD-132
> URL: https://issues.apache.org/jira/browse/MPMD-132
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: CPD, PMD
> Affects Versions: 2.5
> Reporter: Derek Lewis
> Priority: Major
> Attachments: maven-pmd-plugin-bug-2.zip, maven-pmd-plugin-bug.zip
>
>
> When trying to configure cpd and pmd differently (ie. includeTests for PMD, but not for CPD), the plugin does not honour configuration within the execution.
> For example, if a ruleset file is specified in <configuration> within the <execution>, it is ignored, and the default ruleset is applied.
> In the testcase:
> $ mvn install
> ^ This fails with a PMD error, because the ruleset is ignored due to the <configuration> being within the <execution>
> $ mvn install -Pwith-pmd-that-works
> ^ This passes, because it is a profile where the <configuration> is within <plugin>, not <execution>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)