John Patrick created MPMD-190:
---------------------------------
Summary: Seperate CPD configuration from PMD i.e. exclude/include
paths
Key: MPMD-190
URL: https://jira.codehaus.org/browse/MPMD-190
Project: Maven PMD Plugin
Issue Type: Bug
Components: CPD
Affects Versions: 3.2
Environment: n/a
Reporter: John Patrick
CPD highlights lots of warnings in our jpa entity packages and also out dto
builders. This is correct lots of tables have the same fields. We can exclude
them but this also excludes pmd, ideally we just want to exclude the following
paths from CPD but still have PMD checked on them.
**/data/entity/*.java
**/data/builder/*.java
I see two options, either both pmd and cpd get their own nested
<configuration>, or cpd it split into it's own top level plugin. I realise
splitting the plugin is a lot of work so giving the option to have their own
nest configuration might be simpler...
We have about 1000 cpd warnings, of which 90% are specifically around jpa
entities or dto builders. Jenkins reports issues but we have the threshold so
high it makes it useless...
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
