4 spaces intent... no tabs... plz!!!!!
--jason
On Jun 25, 2009, at 9:03 PM, Nicholas L Gallardo wrote:
+1, emphatically. I would much rather we agree on code styles now
than reformatting the tree later on. Committing patches gets more
complicated than it needs to be if you wait.
-N
Nicholas Gallardo
WebSphere - REST & WebServices Development
[email protected]
Phone: 512-286-6258
Building: 903 / 5G-016
Bryant Luk <[email protected]>
Bryant Luk <[email protected]>
06/25/2009 08:57 AM
Please respond to
[email protected]
To
[email protected]
cc
Subject
Eclipse code formatter?
Hi,
Anyone got an Eclipse code formatter that we want to use? Maybe
opening a can of worms but I figure it's better that any incoming
patches can be pre-formatted with a code style that everyone
"tolerates" =) so we can easily do diffs.
Mike made one at
http://svn.apache.org/repos/asf/incubator/wink/contrib/ibm-jaxrs/resources/eclipse/eclipse_code_format_apache.xml
that matches what some other Apache projects use. I forget the line
break (might just be 80) instead of 100 as mentioned in the
http://cwiki.apache.org/confluence/display/WINK/Coding+Guidelines but
that can be changed.
--
- Bryant Luk
