To complete about what my accidental email was about: a draft of Java
coding convention for OpenJDK is available there:
http://cr.openjdk.java.net/~alundblad/styleguide/
Those coding conventions are less detailed than Google's one, but give
an interesting level of flexibility. For example they said that the line
length limit may sometime by exceeded if strict compliance with the
limit would reduce readability.
We have not yet discussed about what could be coding convention for SIS.
I suggest to wait for the OpenJDK coding conventions to be final. Then
we could use those conventions as a basis for SIS ones, by enumerating
the differences between OpenJDK and SIS conventions. Examples of aspects
that may differ is the use of Unicode characters (instead than
restricting to 7-bits ASCII).
A next step could be to enable Checkstyle rules for the agreed coding
conventions. SIS currently have coding rules only for the following:
* No tab characters
* New line at end of file
* No redundant imports
* Check for whitespace around generic tokens
Martin
