You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2013/12/19 15:42:09 UTC

[jira] [Updated] (TAJO-164) Maven plugin for code style

     [ https://issues.apache.org/jira/browse/TAJO-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyunsik Choi updated TAJO-164:
------------------------------

    Priority: Major  (was: Minor)

> Maven plugin for code style
> ---------------------------
>
>                 Key: TAJO-164
>                 URL: https://issues.apache.org/jira/browse/TAJO-164
>             Project: Tajo
>          Issue Type: Improvement
>            Reporter: Sergio Esteves
>
> While merging some code, I've been noticing that different developers (including me) have been using different styles.
> Examples:
> a)
> {code}
> switch(...) {
>   case ...
> {code}
> instead of
> {code}
> switch(...) {
> case ...
> {code}
> b) "private long estimateSizeRecursive(TaskAttemptContext ctx, String [] tableIds) {" <- space between "String" and "[]".
> c) Mixing tabs with spaces.
> d) 
> {code}
> import org.apache.hadoop.yarn.state.*;
> {code}
> instead of
> {code}
> import org.apache.hadoop.yarn.state.InvalidStateTransitonException;
> import org.apache.hadoop.yarn.state.MultipleArcTransition;
> import org.apache.hadoop.yarn.state.SingleArcTransition;
> import org.apache.hadoop.yarn.state.StateMachine;
> import org.apache.hadoop.yarn.state.StateMachineFactory;
> {code}
> I think it might be useful, to ensure everyone is adopting the same style, to include a maven plugin to check if the code style is in accordance with tajo rules (e.g., http://maven.apache.org/plugins/maven-checkstyle-plugin/ ).



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)