You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Steinar Bang (JIRA)" <ji...@apache.org> on 2019/04/02 21:32:00 UTC

[jira] [Comment Edited] (MNG-6622) 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

    [ https://issues.apache.org/jira/browse/MNG-6622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808162#comment-16808162 ] 

Steinar Bang edited comment on MNG-6622 at 4/2/19 9:31 PM:
-----------------------------------------------------------

Now I've had a successful "mvn release:perform" on the authservice project:
# The pom.xml files have weird line endings (ie. lf on first and last line and crlf on the rest of the lines) after "mvn release:perform" completion 
# The diffs of the commit only show the changed lines
# The pom.xml files don't show up as modified in git status
# Changing the line endings of the files from crlf to lf only, doesn't make the changed files show up as modified in magit-status, but makes the files show up as unstaged modified in "git status"
# However doing this, puts the pom.xml files back to normal (ie. lf only):
{noformat}
git rm -rf --cached .
git reset --hard HEAD
{noformat}

So what's committed is OK, but the pom.xml files in the working directory are in a strange state.  This is maven 3.6.0.



was (Author: sb@dod.no):
Now I've had a successful "mvn release:perform" on the authservice project:
# The pom.xml files have weird line endings (ie. lf on first and last line and crlf on the rest of the lines) after "mvn release:perform" completion 
# The diffs of the commit only show the changed lines
# The pom.xml files don't show up as modified in git status
# Changing the line endings of the files from crlf to lf only, doesn't make the changed files show up as modified in magit-status, but makes the files show up in "git status"
# However doing this, puts the pom.xml files back to normal (ie. lf only):
{noformat}
git rm -rf --cached .
git reset --hard HEAD
{noformat}

So what's committed is OK, but the pom.xml files in the working directory is in a strange state.  This is maven 3.6.0.


> 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: MNG-6622
>                 URL: https://issues.apache.org/jira/browse/MNG-6622
>             Project: Maven
>          Issue Type: Bug
>    Affects Versions: 3.3.9
>         Environment: debian 9.8 "stretch", amd64, openjdk 8u212-b01-1~deb9u1, maven 3.3.9-4
>            Reporter: Steinar Bang
>            Priority: Major
>
> 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
(v7.6.3#76005)