maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <>
Subject [jira] Commented: (MWAR-164) suporting spesification of encoding to use when filtering resources
Date Tue, 10 Feb 2009 13:50:19 GMT


Dennis Lundberg commented on MWAR-164:

Bug fix for filteringDeploymentDescriptors coming up.

> suporting spesification of encoding to use when filtering resources
> -------------------------------------------------------------------
>                 Key: MWAR-164
>                 URL:
>             Project: Maven 2.x War Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.1-alpha-1
>            Reporter: kai lilleby
>             Fix For: 2.1
> Quoting Hervé:
> {quote}
> 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 as a default
> value is a good idea.
> Seems like this is worth a Jira issue to track this new feature.
> {quote}

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message