Mailing-List: contact dev-help@sqoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@sqoop.apache.org
Received-SPF: pass (nike.apache.org: domain of gshapira@cloudera.com
 designates 209.85.213.49 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADgZ+QnsWKJ5uxDktixxp-qXJwJbBfbHEeaSL1g1hV4vzpuqLg@mail.gmail.com>
References: 
 <CADgZ+QnsWKJ5uxDktixxp-qXJwJbBfbHEeaSL1g1hV4vzpuqLg@mail.gmail.com>
Date: Sun, 30 Nov 2014 16:46:20 -0800
Message-ID: 
 <CAHBV8We3WU9bZxxHpwSbNHH-d4BTt29m225ZP47GkWFke5+2Qg@mail.gmail.com>
Subject: Re: Sqoop 2 JAVA coding guidelines
From: Gwen Shapira <gshapira@cloudera.com>
To: "dev@sqoop.apache.org" <dev@sqoop.apache.org>
Content-Type: text/plain; charset=UTF-8

I think its a great idea to document the coding standards that already
exist for this project.
It can be frustrating to new contributors to have to guess their way
around our un-written expectations.

Gwen

On Sun, Nov 30, 2014 at 2:05 PM, Veena Basavaraj
<vbasavaraj@cloudera.com> wrote:
> Hey all,
>
> Since a few months I have been contributing to Sqoop2, I do notice a lack
> of style guide for sqoop2 code.
>
> I have started a wiki highlighting things for developers to follow.
>
> https://cwiki.apache.org/confluence/display/SQOOP/Sqoop+2+Coding+Guidelines
> I prefer the google java style guide to begin with.
>
> Please add your comments in the comments section on things you would like
> to have, so we can iterate over this in the coming few weeks and settle
> down to a standard that every one can use in their IDE. I am happy to
> create a formatter XML for eclipse as per these rules and attach it to the
> wiki.
>
>
>
> Best,
> *./Vee*