[jira] (MASSEMBLY-736) Files are read using ${file.encoding} instead of configured encoding

[JIRA]

    [ 
https://jira.codehaus.org/browse/MASSEMBLY-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358307#comment-358307
 ] 

Jörg Sesterhenn edited comment on MASSEMBLY-736 at 12/1/14 2:31 AM:
--------------------------------------------------------------------

We experienced this not in properties but in a windows batch file (start.bat) 
with the content beeing:
{code}
@echo off
call ..\..\sysconfig\setenv.cmd
cd %~dp0%
start "Gelöschte Verträge" %JAVAEXE%  
../lib/geloeschtevertraege-dienst.jar  ./ %JAVAOPTS% 
exit
{code}

The file was edited and saved in ISO-8859-15 which is very similar to cp1252.

The "ö" got filtered correctly on a windows client (where file.encoding 
was cp1252) but was messed up on our linux (sles11) build server (where 
file.encoding was utf-8).
project.build.sourceEncoding was ISO-8859-15.

We fixed the build by adding "-Dfile.encoding=ISO-8859-15" on the command line, 
but this being platform dependent felt like a bug to me.


was (Author: joerg.sesterhenn):
We experienced this not in properties but in a windows batch file (start.bat) 
with the content beeing:
{code}
@echo off
call ..\..\sysconfig\setenv.cmd
cd %~dp0%
start "Gelöschte Verträge" %JAVAEXE%  ../lib/geloeschtevertraege-dienst.jar 
 ./ %JAVAOPTS% 
exit
{code}

The file was edited and saved in ISO-8859-15 which is very similar to cp1252.

The "ö" got filtered correctly on a windows client (where file.encoding 
was cp1252) but was messed up on our linux (sles11) build server (where 
file.encoding was utf-8).
project.build.sourceEncoding was ISO-8859-15.

We fixed the build by adding "-Dfile.encoding=ISO-8859-15" on the command line, 
but this being platform dependent felt like a bug to me.

> 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)