Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 52053 invoked from network); 16 Jun 2004 17:25:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 16 Jun 2004 17:25:37 -0000 Received: (qmail 69884 invoked by uid 500); 16 Jun 2004 17:25:39 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 69810 invoked by uid 500); 16 Jun 2004 17:25:37 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 69721 invoked by uid 99); 16 Jun 2004 17:25:35 -0000 Received: from [205.160.101.145] (HELO hqexch01.upstate.com) (205.160.101.145) by apache.org (qpsmtpd/0.27.1) with ESMTP; Wed, 16 Jun 2004 10:25:35 -0700 Received: from IQUITOS (81-202-96-235.user.ono.com [81.202.96.235]) by hqexch01.upstate.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id J9LRQP7A; Wed, 16 Jun 2004 13:27:54 -0400 Reply-To: From: "Eric Pugh" To: "Jakarta Commons Developers List" Subject: RE: [configuration] Code conventions Date: Wed, 16 Jun 2004 19:25:07 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <20040616092412.J91354@minotaur.apache.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I checked, and you can tell CheckStyle to fail things if there are failures.. If we are going to do it, then let's do it whole hog and make that part of the build.. What do you think.. Go with the sun standard? (simplifies IDE's etc). Eric > -----Original Message----- > From: Martin Cooper [mailto:martinc@apache.org] > Sent: Wednesday, June 16, 2004 6:28 PM > To: Jakarta Commons Developers List > Subject: Re: [configuration] Code conventions > > > > > On Wed, 16 Jun 2004, Emmanuel Bourg wrote: > > > There is no uniform code style in [configuration], most of the > time the block > > bracket is put on a new line, and sometimes it is found at the > end of the > > line like most other commons projects. > > > > What convention should we adopt? I have no personal preference. > > You can choose whatever coding standards you like for a particular > component. Per the Commons Guidelines, the default is the Sun coding > conventions. If you want to use something else, you need only document > what you decide to use, so that others can follow it (and Checkstyle can > be made to check it). See item 19 here: > > http://jakarta.apache.org/commons/charter.html#Guidelines > > -- > Martin Cooper > > > > > > Emmanuel Bourg > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org > > For additional commands, e-mail: commons-dev-help@jakarta.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: commons-dev-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org