[
https://jira.codehaus.org/browse/MWAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282029#comment-282029
]
Nicolas Marcotte commented on MWAR-81:
--------------------------------------
That the workaround that motivating myself to write that patch since I moved
from atrocities like that:{code:xml}
<packagingExcludes combine.self="override">
**/A*.jar,**/B*.jar,**/C*.jar,**/M*.jar,**/O*.jar,
**/*P*.jar,**/R*.jar,**/a*.jar,**/b*.jar,**/c*.jar,
**/d*.jar,**/f*.jar,**/k*.jar,**/i*.jar,**/j*.jar,
**/l*.jar,**/m*.jar,**/r*.jar,**/sa*.jar,**/se*.jar,
**/v*.jar,**/x*.jar,
<!-- to exclude struts patched for RAD but not the lib's patched for our prod
environment that's ends with .SIRUS-->
**/Struts-Layout.jar,**/struts-menu.jar,**/struts.jar
</packagingExcludes>
{code}
to
{code:xml}
<packagingExcludes>**/*.jar,!**/*.SIRUS.jar</packagingExcludes>
{code}
> Request enhancement to pattern matching for
> warSourceIncludes/warSourceExcludes 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
