apache / apache/maven-pmd-plugin

Provide individual configuration settings for PMD/CPD excludes

Open
#680 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Java
Stars
66
Forks
55
Avg merge
8d 16h
Merged PRs (30d)
7

Description

### New feature, improvement proposal

As of now the configuration of the plugin only has one configuration parameter to set the exclude, named ``.

The format of excludes are different for CPD and PMD, so you need two different supression files for both executions during build and for all report sets during report generation.
This results a blown up plugin configuration, because it's the only configuration you can't set in pluginManagement.

```xml



org.apache.maven.plugins
maven-pmd-plugin
3.28.0




true
true
${dev.noSCA}
${dev.scaFailBuild}





org.apache.maven.plugins
maven-pmd-plugin



pmd_check
verify

pmd


${session.executionRootDirectory}/exclude-pmd.properties



cpd_check
verify

cpd


${session.executionRootDirectory}/exclude-cpd.properties







org.apache.maven.plugins
maven-pmd-plugin


pmd

pmd


${session.executionRootDirectory}/exclude-pmd.properties



cpd

cpd


${session.executionRootDirectory}/exclude-cpd.properties




aggregate

false

aggregate-pmd-no-fork


${session.executionRootDirectory}/exclude-pmd.properties



aggregate-cpd

false


aggregate-cpd


${session.executionRootDirectory}/exclude-cpd.properties





```

It would be great to have two properties for the plugin configuration, like
`excludeFilePMD` and `excludeFileCPD`, so it's possible to set those only once in the plugin configuration.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.