maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason van Zyl (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-841) Support customization of default excludes
Date Sun, 19 Jan 2014 21:15:49 GMT

     [ https://jira.codehaus.org/browse/MNG-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jason van Zyl closed MNG-841.
-----------------------------

    Resolution: Incomplete
    
> Support customization of default excludes
> -----------------------------------------
>
>                 Key: MNG-841
>                 URL: https://jira.codehaus.org/browse/MNG-841
>             Project: Maven 2 & 3
>          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
>             Fix For: Issues to be reviewed for 4.x
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message