Eclipse has the lovely Source->Format option which can do everything for us, but it does make it a bit harder to compare one version of Xith3D to another depending on how many formatting changes this would make.
I like the Source->Format option.
Source -> Add Javadoc Comment is useful, too. Eclipse also has the advantage that the code conventions can be saved in an xml-file. Version comparing can get a bit more difficult, but as the format will only change once per file (depending how much the files differ from the conventions) it isn't such a big problem and makes the code more readable.
I suggest taking the following simple steps:
- create a simple "(not yet) official code conventions" page at xith.org
- write a paragraph in the xith.org docs section linking to this new page
- create a new thread in this forum where everyone can write down suggestions for exceptions from the Sun code conventions (or more detailed explanations if necessary)
- after a fixed time span without new suggestions the code conventions become official
Of couse it would also be nice, if people can download code convention files for eclipse (or other IDEs), when they start to differ from Sun conventions for which eclipse has built-in support. Are you happy with this procedure?