-
Notifications
You must be signed in to change notification settings - Fork 302
Added possibility to specify encoding for generated git.properties file #131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…t.json file. If no encoding is configured, platform encoding will be used as before. Resolves git-commit-id#130
Hello @ffriedrich, as discussed in #130 (comment), let's just make sure we use UTF-8 everywhere instead of exposing another option (this plugin has way too many plugins already :-)). Thanks a lot for digging into this, awaiting an updated PR! |
Ok, I have updated the pull request and set the encoding to UTF-8. |
File gitPropsFile = craftPropertiesOutputFile(base, propertiesFilename); | ||
try { | ||
Files.createParentDirs(gitPropsFile); | ||
|
||
fileWriter = new FileWriter(gitPropsFile); | ||
outputWriter = new OutputStreamWriter(new FileOutputStream(gitPropsFile), Charset.forName("UTF-8")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use guava's Charsets.UTF_8
instead of strings here :)
Looks good in general, would you mind fixing the one issue I pointed out and squashing this into one commit? I'll merge once I get internet again :-) |
Added possibility to specify encoding for generated git.properties file
Got hotel internet working, let's merge this :-) |
cool, thank you! |
.. and git.json file.
If no encoding is configured, platform encoding will be used as before.
Resolves #130