Hi, 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. Regards, Hervé Le mardi 05 août 2008, Stephane Nicoll a écrit : > Howdy, > > Hervé, could you please give us a status of the work needed to upgrade war > to support filtered encoding? We are using maven filtering so will it come > "for free" in the next release? > > Best, > Stéphane > > ---------- Forwarded message ---------- > From: Kai Lilleby <[EMAIL PROTECTED]> > Date: Tue, Aug 5, 2008 at 8:57 AM > Subject: regarding encoding and filtering in maven war plugin > To: [EMAIL PROTECTED] > > > Greetings from norway:) > any idea on when spesification of encoding to use when filtering war > resources will be supported? > seems that current version uses the system default encoding.. > > kai --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
