I updated the following equinox projects
to have the latest Equinox code convention settings. I also updated
each project to format java files when saving. You may notice additional
changes when saving java files and creating patches. In this case
the code was probably not correctly formatted.
Because of bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=200207
the org.eclipse.osgi project cannot set the "Malformed Javadoc"
compiler settings to "Error". All other projects do have
this set to "Error".
John Arthorne <John_Arthorne@xxxxxxxxxx> Sent by: equinox-dev-bounces@xxxxxxxxxxx
08/20/2007 04:35 PM
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
In some ways these sort of guidelines can show up as restricting one's
freedom of artistic code formatting or variable naming _expression_. In practice
however, having a common set of coding practices is one of the ingredients
of our success. We have a large and growing body of committers in Equinox,
and a much larger community looking in and trying to understand what we
write. Having common and consistent conventions makes our code easier
to read and work with for everyone.
In particular, check out the section around formatter and compiler settings.
These we should setup in each project so that everyone is seeing the same
errors and formatting the same way. We're also going to experiment with
enabling automatic formatting and code cleanup on save, so we can just
forget about these issues and let the tools do the work.
equinox-dev mailing list