Source code with a consistent look-and-feel makes it easier for people to join 
the project community and contribute.

Let’s continue to keep reformatting commits separate from logic 
changes—otherwise it’s too hard to review.


> On Oct 12, 2016, at 10:06 AM, Dan Smith <> wrote:
> +1
> This might be a good time to reformat the code since I don't think there
> are too many long lived feature branches outstanding.
> -Dan
> On Wed, Oct 12, 2016 at 10:00 AM, Jared Stewart <> wrote:
>> I would like to advocate for adding a Checkstyle <http://checkstyle.
>>> or Spotless <>
>> gradle task to our build process to ensure that all code checked in meets
>> the formatting standards described on the wiki <
>> confluence/display/GEODE/Code+Style+Guide> (and in the intellij/eclipse
>> formatter xml files in our repository). This will alleviate difficulties
>> reviewing code when whitespace or formatting has changed since all code
>> checked in will already comply with standards.

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to