Hi Ian, Thanks for providing this. This is very much appreciated.
It is probably about time to start thinking and fighting about such a thing as a coding convention ... Ian Boston schrieb: > For what it is worth, and I wont say I agree with all of it, but thats ok. > > The shindig eclipse files are here > http://svn.apache.org/repos/asf/incubator/shindig/trunk/etc/eclipse/ > but you probably wont want the import order as it reverses to allow > overrides. > > and there is a checkstyle config > http://svn.apache.org/repos/asf/incubator/shindig/trunk/etc/checkstyle/checkstyle.xml > > which is almost right. > > There is a description of the thought process > http://cwiki.apache.org/SHINDIGxSITE/java-style.html (mentions 4 and 2 > space indents) > > > YM -will- V > Ian > > I hope I haven't opened up pandora's box :) It may well be, but in the end, sooner or later this box would have been opened upon us anyway ;-) So no worry. To track this I created SLING-937 [1]. Feel free to add to this... Regards Felix [1] https://issues.apache.org/jira/browse/SLING-937 > > On 22 Apr 2009, at 17:48, Felix Meschberger wrote: > >> Hi Ian, >> >> Ian Boston schrieb: >>> Is there a code style guide for sling, or better still an eclipse config >>> and import order. >>> It looks like standard java style but I am not sure about the space >>> policy. >> >> Interesting topic which is as important as it is controverse. >> >> As Bertrand, I am basically using the default Eclipse Setup. What I >> think is very important is the no-tab policy (I think we are pretty much >> in agreement nowadays, that tabs are bad ;-) ) >> >> Another thing is the formatting of comments and the line length. The >> default in Eclipse is something like 80. In Apache Felix we have >> something like 120. >> >> Sometimes I have the impression, that 120 would be better than 80 for >> editing etc. But then I am hooked on my own personal vt100 legacy >> thinking ;-) >> >> Regards >> Felix > >
