tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henry Saputra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAJO-76) Coding Convention
Date Fri, 12 Jul 2013 00:27:48 GMT

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

Henry Saputra commented on TAJO-76:
-----------------------------------

I think this should be a good start. The other things are not really convention but more into
requirements such as adding Apache license header, comment for new classes and methods.
                
> Coding Convention
> -----------------
>
>                 Key: TAJO-76
>                 URL: https://issues.apache.org/jira/browse/TAJO-76
>             Project: Tajo
>          Issue Type: Task
>            Reporter: Hyunsik Choi
>
> We need to discuss coding conventions.
> I would like to suggest Sun's code conventions [1] with the following exceptions:
>  * 2 spaces indentation instead of 4 spaces
>  * 100 char limit per line instead of 80
> [1] http://www.oracle.com/technetwork/java/javase/documentation/codeconvtoc-136057.html

--
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