I guess it is okay to rehash formatting standards every couple of years, so this is what I'm hearing:
1) The only thing that has anything close to consensus on is that we should disable formatting for block and line comments. 2) Field alignment sounds like the people who want it disabled are passionate about it, and those that like it the way it is can deal if we change it. Sounds like we can give it a try 3) It seems like there are votes for each extreme on method/cstr parameters, so I'm inclined to leave the current setting alone which is middle ground IMO. _____ From: Tim Eck [mailto:[EMAIL PROTECTED] Sent: Friday, October 26, 2007 3:50 PM To: [email protected] Subject: eclipse .classpath, etc I committed new versions of all our .classpath files in trunk. I wrote a program that uses modules.def.yml and the various ivy dependency descriptors and generates .classpath for each module. Some of this effort might be redundant when and if we ever use maven to drive our build, but that day is not today :-) I intend to also standardize the .settings files (ie. compiler options, warnings, formatting, etc) across our eclipse projects as well. Let me know if this update breaks anything in eclipse. -tim
_______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
