[
https://issues.apache.org/jira/browse/MRELEASE-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718349#comment-14718349
]
Alexander Kriegisch commented on MRELEASE-899:
----------------------------------------------
I am a user, not a maintainer. I am reporting a backward compatibility issue.
Why are you dismissing it like it was nothing and I was too stupid to use your
plugin or Git correctly?
BTW, I have created a corresponding issue
[here](https://github.com/git-for-windows/git/issues/315). Maybe you can talk
to the Git for Windows maintainer and sort it out together so as to get it
working again.
> release:prepare should not change the line separator
> ----------------------------------------------------
>
> Key: MRELEASE-899
> URL: https://issues.apache.org/jira/browse/MRELEASE-899
> Project: Maven Release Plugin
> Issue Type: Improvement
> Reporter: Ralph van Etten
>
> Currently the plugin use the system property {{line.separator}} when it
> rewrites the pom.xml.
> This causes trouble, because every line in changed, when a project is
> released sometimes under Windows and sometimes under Linux (because of its
> different line separators).
> (http://stackoverflow.com/questions/11868590/maven-release-plugin-and-windows-line-breaks)
> Therefore it would be a nice feature when the plugin would not use the
> systems line separator but the line separator that is already used in the
> pom.xml.
> On the other hand, changing the existing behaviour would maybe, also harm
> someone else.
> Therefore it would be an great feature when there would be an property that
> define the expected behaviour, maybe in the same way it is done by the
> maven-assembly-plugin's property fileSet.lineEnding
> (http://maven.apache.org/plugins/maven-assembly-plugin/component.html#class_fileSet)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
