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

Support for specifying which encoding to use when filtering resources

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.1-alpha-1
    • Fix Version/s: 2.3
    • Component/s: filtering
    • Labels:
      None

      Description

      Quoting Hervé:

      Maven filtering provides an encoding parameter to set encoding used when
      reading/writing files. But war plugin uses null value, which means platform
      encoding... Sorry, encoding support won't be totally "free"

      I added TODOs in the code.

      For web.xml and container config XML file, I set encoding to UTF-8, which is a
      better default value than platform encoding.

      For other filtered resources, you'll need to add an encoding attribute to
      o.a.m.model.Resource class, to let the user define which encoding he wants to
      use when filtering. Perhaps using project.build.sourceEncoding as a default
      value is a good idea.
      Seems like this is worth a Jira issue to track this new feature.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                dennisl@apache.org Dennis Lundberg
                Reporter:
                kai@systemfabrikken.no Kai Lilleby
              • Votes:
                12 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: