[
https://jira.codehaus.org/browse/MASSEMBLY-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358225#comment-358225
]
Kristian Rosenvold commented on MASSEMBLY-736:
----------------------------------------------
All regular files are interpolated using project.build.sourceEncoding, as you
expect.
There is an exception for .properties files, which by definition are ISO-8859-1.
There appears to be a bug in this area; it seems like properties files are also
interpolated with project.build.sourceEncoding,
is this the problem you were experiencing ? (You'd get UTF8 written into the
property file, which in turn would be mangled by java when the file is read
back...)
> Files are read using ${file.encoding} instead of configured encoding
> --------------------------------------------------------------------
>
> Key: MASSEMBLY-736
> URL: https://jira.codehaus.org/browse/MASSEMBLY-736
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: maven-archiver
> Affects Versions: 2.5.1
> Environment: Windows 7 / SLES 11
> Reporter: Jörg Sesterhenn
>
> Maven (and the assembly plugin) read files with the encoding that is present
> in the system variable "file.encoding", although
> "project.build.sourceEncoding" was set to a different value. That leads to
> assemblies being dependent on the (build) plattform.
> In our build we had a file that got filtered and included in the build, but
> due to being read with the wrong encoding during assembly all umlauts got
> broken.
> Please fix this. "project.build.sourceEncoding" should be used to read files
> into the assembly by default (as documented).
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
