incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Bachmann-Gmür (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CLEREZZA-435) Coding convention compliance
Date Wed, 05 Dec 2012 10:58:58 GMT

    [ https://issues.apache.org/jira/browse/CLEREZZA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510418#comment-13510418
] 

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

Wondering what defaults we could use, the stanbol eclipse defaults are here: http://svn.apache.org/repos/asf/stanbol/trunk/conventions/stanbol-eclipse-codeformatter.xml.
Netbeans uses thecheckstyles rules configured in maven.
                
> Coding convention compliance
> ----------------------------
>
>                 Key: CLEREZZA-435
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-435
>             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
committer.
> 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: http://www.atlassian.com/software/jira

Mime
View raw message