[
https://jira.codehaus.org/browse/MWAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282222#comment-282222
]
Joerg Schaible edited comment on MWAR-81 at 10/27/11 9:06 AM:
--------------------------------------------------------------
This is what I mean: You don't have to patch anything, it already works (at
least tested with 2.1.1)! I can use this without any problems to exclude files
with log4j in their names:
{noformat}
<packagingExcludes>%regex[.*log4j.*]</packagingExcludes>
{noformat}
was (Author: joehni):
This is what I mean: You don't have to patch anything, it already works! I
can use this without any problems to exclude files with log4j in their names:
{noformat}
<packagingExcludes>%regex[.*log4j.*]</packagingExcludes>
{noformat}
> Request enhancement to pattern matching for
> packagingIncludes/packagingExcludes functionality (regular expressions?)
> --------------------------------------------------------------------------------------------------------------------
>
> Key: MWAR-81
> URL: https://jira.codehaus.org/browse/MWAR-81
> Project: Maven 2.x WAR Plugin
> Issue Type: Wish
> Environment: n/a
> Reporter: Bryan Loofbourrow
> Priority: Minor
> Attachments: maven-war-plugin-2.1.1-NM.patch
>
>
> The Maven War Plugin currently permits choosing what files will wind up in
> the .war. It does this via two parameters, warSourceIncludes, and
> warSourceExcludes. The rule appears to be that the includes are computed,
> and a list of matches made, then that list is run against the excludes, and
> any matches taken out of the include list.
> The only wildcards that appear to be supported are *, **, and ?.
> That doesn't work well if you are packaging wars in ears, and therefore want
> to exclude all jars from the war, except for one or two that have to be in
> the war in order to run properly. "Exclude all but foo.jar and bar.jar" just
> doesn't translate well to "here's your simple include template, here's your
> simple exclude template" representation, at least with current wildcards.
> So this is a wish specifically for something to address the "exclude all but
> x, y, and z" need for war source includes/excludes, and a suggestion that it
> might be best to deprecate the warSourceIncludes/warSourceExcludes approach
> in favor of a single parameter that supports regular expressions instead.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
