Text file considered as binary about editorconfig-maven-plugin HOT 4 CLOSED

Thanks for the report. Clearly, there is a mismatch between the encoding of the file and the encoding the plugin is using. Could you please provide the following info to be able to tell if this is a bug or just a misconfiguration?

(1) What is the encoding of the file?

(2) Have you set the encoding at the Maven level for all files, via editorconfig.encoding or project.build.sourceEncoding property?

(3) Have you set charset in any of the relevant .editorconfig files?

from editorconfig-maven-plugin.

Hi!

(1) What is the encoding of the file?

• With linux file -i: text/plain; charset=iso-8859-1
• With Sublime Text 3: Western (Windows 1252) Unix
• With Eclipse: ISO-8859-1
• With Geany: ISO-8859-1
• With Notepadqq: UNIX / OX S ISO-8859-1

(2) Have you set the encoding at the Maven level for all files, via editorconfig.encoding or project.build.sourceEncoding property?

• My pom.xml contains <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
• I did not set the editorconfig.encoding property (My maven command line was just as it is in the first post)

(3) Have you set charset in any of the relevant .editorconfig files?

Yes. Below is my .editorconfig file (I only have one in the root directory of the app):

root = true

[*]
charset = utf-8
end_of_line = lf
indent_style = space
indent_size = 4
trim_trailing_whitespace = true
insert_final_newline = true

[*.md]
trim_trailing_whitespace = false

[*.yml]
indent_size = 2

from editorconfig-maven-plugin.

Thanks, let me try to reproduce it.

from editorconfig-maven-plugin.

Yes, this is definitely a misconfiguration. You instruct the plugin to handle the file as UTF-8 but in reality the file is ISO-8859-1. It will work if you add something like the following to the bottom of your .editorconfig file:

[*.properties]
charset = iso-8859-1

from editorconfig-maven-plugin.