-Re: Eclipse Code Formatting Guidelines for Apache Flume Source Code
I try to just follow these 4 rules:
1. Lines strictly <= 80 chars
2. No tabs and trailing whitespace
3. Intent - 2 spaces.
4. All if/for etc. have curly braces, even if it is just one line and starting curly braces appear after the if/for/while/try etc in the same line.
You can configure most IDEs to do this automatically for you.
On Saturday, April 6, 2013 at 5:17 AM, Israel Ekpo wrote:
> I wanted to check if this is the current code formatting standards for the
> I stumbled upon the link while reviewing other information in the wiki
> If there are any other recent changes since the initial upload in June 2012
> please let me know.
> I just wanted to make sure that I am up to date with the coding standards
> Some of my earlier patches had formatting issues as pointed out during the
> reviews and I would like to prevent that in subsequent, future patches