You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vincent Massol (JIRA)" <ji...@codehaus.org> on 2011/05/12 19:30:22 UTC
[jira] Commented: (MWAR-81) Request enhancement to pattern matching
for warSourceIncludes/warSourceExcludes functionality (regular
expressions?)
[ http://jira.codehaus.org/browse/MWAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266508#action_266508 ]
Vincent Massol commented on MWAR-81:
------------------------------------
I need this too. My use case:
I want to exclude log4j-<version>.jar but keep the log4j-over-slf4j-<version>.jar...
> Request enhancement to pattern matching for warSourceIncludes/warSourceExcludes functionality (regular expressions?)
> --------------------------------------------------------------------------------------------------------------------
>
> Key: MWAR-81
> URL: http://jira.codehaus.org/browse/MWAR-81
> Project: Maven 2.x WAR Plugin
> Issue Type: Wish
> Environment: n/a
> Reporter: Bryan Loofbourrow
> Priority: Minor
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira