[ https://issues.apache.org/jira/browse/SUREFIRE-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed SUREFIRE-2140. ------------------------------------ Resolution: Fixed Fixed with [c7af2768ba226d4fd9247d150f8bbb34bf64107d|https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=c7af2768ba226d4fd9247d150f8bbb34bf64107d]. > Cannot release Surefire on Windows > ---------------------------------- > > Key: SUREFIRE-2140 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2140 > Project: Maven Surefire > Issue Type: Bug > Affects Versions: 3.0.0-M7 > Reporter: Michael Osipov > Assignee: Michael Osipov > Priority: Major > Fix For: 3.1.0 > > > While trying to release Surefire on Windows today Git failed with: fatal: > CRLF would be replaced by LF in pom.xml > It turns out that the {{.gitattributes}} is: > {noformat} > # Auto detect text files and perform LF normalization > * text eol=lf > *.xml text diff=xml > *.java text diff=java > *.html text diff=html > *.vm text > *.fml text > *.md text > *.css text > *.js text > *.sql text > *.png binary > {noformat} > I don't know why LF is enforced, but most Git clients will perform > {{autocrlf}} and Maven Release Plugin will use platform line separator. > Therefore, it will have CRLF after transformation and Git fails, thus release > fails. I had to perform in Git Bash: > {noformat} > git status | grep modified: | cut -c13- | xargs -I^ dos2unix ^ > {noformat} > through several stages to continue with the release. > Expectation: Either Git will be configured to use LS auto or Maven Release > Plugin will force LF only. -- This message was sent by Atlassian Jira (v8.20.10#820010)