[jira] [Closed] (MENFORCER-184) enforce-(don't)-exist rules should support wildcards

["Michael Osipov (JIRA)" <ji...@apache.org>]

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

Michael Osipov closed MENFORCER-184.
------------------------------------
    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.

> enforce-(don't)-exist rules should support wildcards
> ----------------------------------------------------
>
>                 Key: MENFORCER-184
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-184
>             Project: Maven Enforcer Plugin
>          Issue Type: New Feature
>          Components: Standard Rules
>            Reporter: Martin Höller
>            Priority: Major
>
> With the standard rules enforce-exist and enforce-dont-exist it is possible to ensure files exist resp. do not exist. Unfortunately the files must be specified with the exact name! Wildcards are currently not supported.
> My concrete use case is, I wan't to enforce, that no *Test.class files exist in some output-directory. This is currently not possible. Some configuration like the following should be supported:
> {code}
> <rules>
>   <requireFilesDontExist>
>       <includes>
>         <include>${project.build.outputDirectory}/**/*Test.*</include>
>       </includes>
>     </requireFilesDontExist>
> </rules>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)