Community
Participate
Working Groups
Build Identifier: Currently the xtend-compiler reads the xtend files in a platform dependent encoding. This results in problems when the xtend files are encoded in another encoding. E.g. when the xtend files are saved in ISO-8859-1 encoding, the build runs in problems on a Linus server with another default encoding. Suggestion is to add a parameter to the maven-xtend-compiler for the file encoding. Since the compiler is started in another JVM, the encoding might be passed to the JVM process with a jvm parameter, e.g. -Dfile.encoding=ISO-8859-1. Reproducible: Always Steps to Reproduce: Because xtext uses guillemot brackets («»), all my xtend files are in ISO-8859-1 encoding. Running the maven-xtend-compiler on Windows works fine, but on the Linux build the guillemot characters are not recognized.
have you tried to bind an IEncodingProvider to your language runtime module?
(In reply to comment #1) > have you tried to bind an IEncodingProvider to your language runtime module? He would have to do that for Xtend. We need to provide a property which can be set, which is then used in an IEncodingProvider.
Created attachment 208295 [details] proposed patch since i cannot build the required dependency 'org.eclipse.xtend2.standalone.maven' anymore i will leave a patch here for this - the default encoding value expression is 'project.build.sourceEncoding'
pushed to master
Closing all bugs that were set to RESOLVED before Neon.0
