[MPMD-190] Seperate CPD configuration from PMD i.e. exclude/include paths

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Auto Closed
• Affects Version/s: 3.2
• Component/s: CPD
• Environment: n/a
• Assignee: Unassigned
• Reporter: John Patrick
• Created: 23/Sep/14 04:28
• Updated: 16/Mar/18 22:40
• Resolved: 16/Mar/18 22:40

Description

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...

Issue Links

• is related to: MPMD-132 Cannot configure multiple executions (ie. cpd, pmd) independantly
• is related to: MPMD-133 Parameters for pmd:check/cpd-check should be separate from pmd:pmd/cpd