You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Benedict (JIRA)" <ji...@codehaus.org> on 2014/07/03 17:33:11 UTC
[jira] (MNG-841) Support customization of default excludes
[ https://jira.codehaus.org/browse/MNG-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Benedict updated MNG-841:
------------------------------
Fix Version/s: (was: Issues to be reviewed for 4.x)
> Support customization of default excludes
> -----------------------------------------
>
> Key: MNG-841
> URL: https://jira.codehaus.org/browse/MNG-841
> Project: Maven
> Issue Type: Improvement
> Components: POM
> Affects Versions: 2.0-alpha-3
> Environment: WinXP SP2, Java 1.5, Maven 2.0-alpha-3
> Reporter: John Fallows
>
> Our company uses a home-grown version control system that has it's own per-directory admin subdirectory, similar in purpose to the administration subdirectories used by other version control systems, eg. CVS, .svn, etc.
> These directories are excluded from processing by default in Maven2, and we would like to add our custom admin subdirectory to the default exclusion list.
> Recommended solution from Maven Users Mailing List:
> Brett Porter wrote:
> # What you really need is to be able to configure it in a root POM shared by all projects, I think.
> Hopefully, any such entry in pom.xml would not completely replace the default excludes list, but merely entend the built-in definition.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)