when that is implemented, I would recommend using git attributes to enforce the eol behavior, so that that part is not dependent on a specific editor.
all you would need is a .gitattributes file in the root path with a few entries like this: *.java text *.jsp text that will normalize the text files to LF line endings for storing in the repo. -Daniel On Dec 4, 2011, at 11:03 PM, Scott Battaglia wrote: I was working on creating an Eclipse file that had all those settings. I'm normally an IntelliJ user and was having some issues with the Maven2 plugin for Eclipse. On Tue, Nov 29, 2011 at 2:31 PM, Marvin Addison <marvin.addi...@gmail.com<mailto:marvin.addi...@gmail.com>> wrote: > Only a few of those files had a lot of lines changed. I'd guess that they > had a different EOL than most, and you made them consistent. I do hope we'll take on the task at some point to conform whitespace across the CAS codebase. While it may well be a holywar of tab vs space and CRLF versus LF, I think the consistency in the end will be worth the effort and will reduce the likelihood of issues like this. M -- You are currently subscribed to cas-dev@lists.jasig.org<mailto:cas-dev@lists.jasig.org> as: scott.battag...@gmail.com<mailto:scott.battag...@gmail.com> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to cas-dev@lists.jasig.org<mailto:cas-dev@lists.jasig.org> as: daniel.fr...@ccci.org<mailto:daniel.fr...@ccci.org> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
