[ https://issues.apache.org/jira/browse/MRELEASE-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17543695#comment-17543695 ]
Steinar Bang commented on MRELEASE-1025: ---------------------------------------- This issue has been fixed by MRELEASE-1056, which has moved maven-release-plugin from JDom 1 to JDom 2. I have verified that doing a release with maven-release-plugin 3.0.0-M5 does not mess up the line endings of the pom files. > release:prepare and release:update-version sets line endings to crlf for all > lines except the first and last lines of the pom.xml files > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: MRELEASE-1025 > URL: https://issues.apache.org/jira/browse/MRELEASE-1025 > Project: Maven Release Plugin > Issue Type: Bug > Affects Versions: 2.5.3 > Environment: debian 9.8 "stretch", amd64, openjdk 8u212-b01-1~deb9u1, > maven 3.3.9-4 > Reporter: Steinar Bang > Priority: Major > Labels: debian-issue > > For these two projects > * https://github.com/steinarb/authservice > * https://github.com/steinarb/osgi-service > line endings in the pom.xml files are messed up when I do > {noformat} > mvn release:prepare > {noformat} > or bump versions with e.g. > {noformat} > mvn --batch-mode release:update-versions -DdevelopmentVersion=1.0.2-SNAPSHOT > {noformat} > What happens to the line endings are: > # First line stays at lf > # Last line stays at lf > # All of the intervening lines get crlf > # The line endings were initially lf (at least they were meant to be) > # I run the "mvn release:prepare" and "mvn:update-version" commands from a > command line on Debian GNU/linux -- This message was sent by Atlassian Jira (v8.20.7#820007)