Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 19AF9200B26 for ; Mon, 27 Jun 2016 19:22:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 18442160A5B; Mon, 27 Jun 2016 17:22:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 614F6160A54 for ; Mon, 27 Jun 2016 19:22:08 +0200 (CEST) Received: (qmail 13635 invoked by uid 500); 27 Jun 2016 17:22:07 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 13623 invoked by uid 99); 27 Jun 2016 17:22:07 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Jun 2016 17:22:07 +0000 Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id F03731A0110 for ; Mon, 27 Jun 2016 17:22:06 +0000 (UTC) Received: by mail-wm0-f53.google.com with SMTP id f126so109157893wma.1 for ; Mon, 27 Jun 2016 10:22:06 -0700 (PDT) X-Gm-Message-State: ALyK8tIu5OD9GNHTKyyE8ImyVPml2aIKPAvE7I+S2Hh7+Vsx5OvveJnH2d47I1P+OS9xZxJ4ON1orZAiOz2dFg== X-Received: by 10.28.228.86 with SMTP id b83mr11123001wmh.11.1467048125375; Mon, 27 Jun 2016 10:22:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.1.151 with HTTP; Mon, 27 Jun 2016 10:21:45 -0700 (PDT) X-Originating-IP: [130.88.195.197] In-Reply-To: References: From: Stian Soiland-Reyes Date: Mon, 27 Jun 2016 18:21:45 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Reformatting commons-io to single code style ? To: Commons Developers List Content-Type: text/plain; charset=UTF-8 archived-at: Mon, 27 Jun 2016 17:22:09 -0000 +1 if the code is messy or inconsistent, -0 if it's already OK. Personally I wouldn't do the whole code, just tidy in a separate commit per file before editing it. If you do all of them, then we should also add the agreed checkstyle.xml or equivalent code style file, so that it's easy to keep compliance. The code style should be minimal, e.g. mainly just get decent indentation and have consistent line-breaks in the method declaration, but not care too much about things like how if/else blocks are done or the number of () in a && check. On 27 June 2016 at 09:09, Kristian Rosenvold wrote: > This has probably been discussed a million times before, so I'll keep > it short. commons-io has wonderfully inconsistent code style even > within individual code files. > > Once the move to git completes, I'd like to reformat the entire code > base (including javadoc) to a single style. I don't really care which > style, my OCD is about consistency, not about which particular style > is in use :) > > (Is there any kind of intelliJ code style file for commons ?) > > Sorry for disturbing the hornets :) > > Kristian > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > For additional commands, e-mail: dev-help@commons.apache.org > -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons http://orcid.org/0000-0001-9842-9718 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org