[ 
https://issues.apache.org/jira/browse/MPMD-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MPMD-107.
-------------------------------
    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.

> Making includes and excludes overwritable through a maven property
> ------------------------------------------------------------------
>
>                 Key: MPMD-107
>                 URL: https://issues.apache.org/jira/browse/MPMD-107
>             Project: Maven PMD Plugin
>          Issue Type: New Feature
>            Reporter: Volker Fuessler
>            Priority: Minor
>         Attachments: MPMD-107.patch
>
>
> If you work with maven projects it is usefull to configure common things like 
> plugins, dependencies, company information,... in a parent pom. So, in my 
> case, we have 1 parent pom in our company, from which every project has to 
> inherit. 
> In most cases that's it, no other configurations must be made, but sometimes 
> you have to overwrite some includes or excludes of a plugin. In this case you 
> have to overwrite the whole plugin in the projects pom.
> I think, it would be very usefull, if there would be a possibility to 
> overwrite includes and excludes just by using a simple maven property which 
> takes a string with comma separated patterns that should be in- or excluded.
> I patched the plugin but I thought this could be usefull for other people, so 
> I will add an patch here. 
> The patch adds the following properties, which can be used in a maven 
> <properties> section:
> maven.pmd.includesList
> maven.pmd.excludesList
> example:
> ...
>     <properties>
>         <maven.pmd.excludesList>**/some/package/**/*.java, 
> **/generated-sources/**/*.java</maven.pmd.excludesList>
>         ...
>     </properties>
> ...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to