...
This document deals with issues that are important for MyFaces developers and custom component developers.
...
See http://www.apache.org/dev/styleguide.html for the Apache-Wide Coding Style Guide. Everything that is not documented there should be written according to Suns Java Code Conventions at http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html
Here is a formatter profile for eclipse 3.1: [codeconventions4eclipseapache-codeconv.xml] . Import it through Window->Preferences->Java->Code Style->Formatter
Here is a formatter profile for IntelliJ IDEA 7.0 (7718): [MyFacesIdeaSettings.jar] maven-idea-codestyle.xml. Import it through File->Import Settings ... This should add a new profile called "MyFaces"
...
...
Addition special comments (see 10.5.4 in ! CodeConv)
...
Every file should start with the following copyright notice:
...
...
Every class and interface should have a javadoc similar to this:
...
...
Developers should be setting their autoprops so that files have an svn:eol-style of 'native'. Developers working on *nix systems are "lucky" because native on *nix is what SVN calls native, but the autoprops should still be set so that keywords are replaced as well. This is described on the [http://wiki.apache.org/struts/StrutsMaintenanceSvn]. Struts SVN wiki page.
...