incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Bachmann-Gmür (JIRA) <>
Subject [jira] [Commented] (CLEREZZA-435) Coding convention compliance
Date Wed, 28 Nov 2012 09:48:58 GMT


Reto Bachmann-Gmür commented on CLEREZZA-435:

I agree that "A tabulator is used as unit of indentation." is the better solution (more elegant,
more semantic, more accessible, more ecological), however most of the code around us uses
spaces and the tools generally comes with better support for spaces (you can change the configuration
in netbeans and eclipse but not all plugings will honour this). So I'm thinking if we might
compromise here and go for four spaces in java and poms and two spaces in scala. WDYT?
> Coding convention compliance
> ----------------------------
>                 Key: CLEREZZA-435
>                 URL:
>             Project: Clerezza
>          Issue Type: Improvement
>            Reporter: Hasan
>            Priority: Trivial
>         Attachments: zz-coding-conventions.v1.txt
> This issue is about writing code which should comply to certain conventions within Clerezza's
> An initial document on the coding conventions is attached to this issue.
> If you want to update Clerezza code so that it complies with these conventions, please
use this issue number
> when you commit your changes. We might do this every now and then, therefore, please
don't resolve and close this issue.
> Please DON'T use this issue number in your commit, if you also have other changes in
the code besides changes
> due to coding conventions. If you could separate your commit in two steps, then it would
be the best. 
> One for the coding conventions (using this issue number in your commit) and the other
for the fix due to the "real" issue 
> you want to solve (using the respective issue number).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message