Uploaded image for project: 'Maven WAR Plugin'
  1. Maven WAR Plugin
  2. MWAR-81

Request enhancement to pattern matching for packagingIncludes/packagingExcludes functionality (regular expressions?)

    XMLWordPrintableJSON

Details

    • Wish
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • 2.2
    • None
    • None
    • n/a

    Description

      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.

      Attachments

        1. maven-war-plugin-2.1.1-NM.patch
          16 kB
          Nicolas Marcotte
        2. maven-war-plugin-2.1.1-NM-Doc-Test.patch
          5 kB
          Nicolas Marcotte

        Issue Links

          Activity

            People

              dennisl@apache.org Dennis Lundberg
              bryanloof Bryan Loofbourrow
              Votes:
              15 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: