[ https://issues.apache.org/jira/browse/SCM-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963294#comment-17963294 ]
ASF GitHub Bot commented on SCM-834: ------------------------------------ jira-importer commented on issue #1050: URL: https://github.com/apache/maven-scm/issues/1050#issuecomment-2964642879 **[Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)** commented Can someone provide me a sample project configuration? > Commit encoding is platform-dependent instead of UTF-8 > ------------------------------------------------------ > > Key: SCM-834 > URL: https://issues.apache.org/jira/browse/SCM-834 > Project: Maven SCM (Moved to GitHub Issues) > Issue Type: Bug > Components: maven-scm-provider-gitexe, maven-scm-provider-svn > Affects Versions: 1.9.4 > Reporter: Tobias Gruetzmacher > Assignee: Michael Osipov > Priority: Blocker > Fix For: 1.11.1 > > > When doing a release with the maven-release-plugin, if you have a > non-ASCII-character in your commit message (setting scmCommentPrefix to > "lösung" for example), the resulting commit message has a different encoding > on different operating systems. If it isn't UTF-8 (on Windows, for example), > git complains with > {code} > Warning: commit message did not conform to UTF-8. > You may want to amend it after fixing the message, or set the config > variable i18n.commitencoding to the encoding your project uses. > {code} > AFAICS, the fix is pretty simple: Just add "UTF-8" to the call of fileWrite > in > [GitCheckInCommand.java|https://github.com/apache/maven-scm/blob/master/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/checkin/GitCheckInCommand.java#L74] -- This message was sent by Atlassian Jira (v8.20.10#820010)