Bug 58575

Summary:	Set svn:eol-style native on all *.java files
Product:	POI	Reporter:	Javen O'Neal <onealj>
Component:	POI Overall	Assignee:	POI Developers List <dev>
Status:	NEW ---
Severity:	enhancement
Priority:	P2
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux

Description Javen O'Neal 2015-11-03 06:29:27 UTC

Some submitted patches contain lines that differ only by EOL.

Short term fix: recursively set svn:eol-style=native property to all *.java files

In the long term, should we have an SVN pre-commit hook or an ant test to make sure all checked in *.java files have svn:eol-style=native property set, or should we continue setting these properties manually as we remember? Would there ever be a case where a java file shouldn't have svn:eol-style=native set?

Comment 1 Javen O'Neal 2016-06-17 07:25:14 UTC

Added svn:auto-props in r1748802, which will check out files with native line endings if the subversion client >=1.8.

For developers using an older subversion client, they could add the following to their subversion config file:
http://stackoverflow.com/questions/5671406/force-svneol-style-native-on-the-server

Committers should add the following to ~/.subversion/config:
[miscellany]
enable-auto-props = yes

[auto-props]
*.java = svn:eol-style=native