[
https://issues.apache.org/jira/browse/MRELEASE-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712693#comment-14712693
]
Alexander Kriegisch commented on MRELEASE-899:
----------------------------------------------
Well, I prefer to configure my Git with option "check out as-is, commit UNIX".
Other plugins respect the existing line separator in a file, Maven Release also
did when I used it with the previous Git version, but no longer with this one.
It just irritates me to see huge diffs after `release:prepare`. I dislike the
fact that a single Maven plugin decides to change the line separator in all my
POMs while my editors and IDEs as well as other Maven plugins respect it.
> 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)
