[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[incubation] Project Release Coding Style
|
Over on triquetrum-dev, we were discussing coding style.
My impression, which might be wrong, was that code to be released should
follow the Eclipse coding style as defined in the preferences by Java ->
Code Style -> Formatter -> "Eclipse [built-in]" and Java -> Code Style
-> Clean up -> "Eclipse [build-in]"
I imagined that part of the Eclipse release process was to clean the
code and reformat it with the Eclipse coding style.
I work in academia and we see software as a form of publication, so a
consistent coding style as being very important. OTOH, coding style can
be a religious issue. Personally, I don't care what the style is, as
long as there is a tool that will do the cleanup.
Is there a guideline about coding style for Eclipse projects, or is each
project able to choose there own?
I went through the Eclipse Development Process at
https://www.eclipse.org/projects/dev_process/development_process.php#6_3_Reviews
and Development Resources/HOWTO/Release Reviews at
https://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews
but did not see anything.
https://wiki.eclipse.org/Coding_Conventions has a little bit of
information, such as 4 spaces for indents. However, this page seems
incomplete.
A second question is that if the code should be using the "Eclipse
[built-in]" style, then has there been any thought to having Git at
least reformat the code automatically?
_Christopher
--
Christopher Brooks, PMP University of California
Academic Program Manager & Software Engineer US Mail: 337 Cory Hall
CHESS/iCyPhy/Ptolemy/TerraSwarm Berkeley, CA 94720-1774
cxh@xxxxxxxxxxxxxxxxx, 707.332.0670 (Office: 545Q Cory)