From log4j-dev-return-7931-apmail-logging-log4j-dev-archive=logging.apache.org@logging.apache.org Fri Sep 03 12:52:56 2004 Return-Path: Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: (qmail 96656 invoked from network); 3 Sep 2004 12:52:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 3 Sep 2004 12:52:56 -0000 Received: (qmail 99267 invoked by uid 500); 3 Sep 2004 12:52:53 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 99193 invoked by uid 500); 3 Sep 2004 12:52:52 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 99159 invoked by uid 99); 3 Sep 2004 12:52:52 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [63.244.250.133] (HELO warhawk.mpi.com) (63.244.250.133) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 03 Sep 2004 05:52:51 -0700 Received: from lightning.mpi.com (lightning [63.244.252.11]) by warhawk.mpi.com (Switch-3.1.6/Switch-3.1.6) with ESMTP id i83CqmZs016917 for ; Fri, 3 Sep 2004 08:52:48 -0400 (EDT) Received: from US-VS1.corp.mpi.com (us-be2.corp.mpi.com [63.244.252.32]) by lightning.mpi.com (Switch-3.1.6/Switch-3.1.6) with ESMTP id i83Cqgvq006153 for ; Fri, 3 Sep 2004 08:52:45 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [POLL] Source code formatting conventions Date: Fri, 3 Sep 2004 08:52:45 -0400 Message-ID: <9C5166762F311146951505C6790A9CF80229C00E@US-VS1.corp.mpi.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [POLL] Source code formatting conventions Thread-Index: AcSRshkl61GjgUy3S+qTJwh4N7nJHgAAlIjw From: "Shapira, Yoav" To: "Log4J Developers List" X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N H= i, You're right that development has stopped on the open-source version o= f Jalopy, and that's a negative. However, Jalopy still works well and= IIRC still supports a superset of the Eclipse formatting features. We don't want to require log4j developers to use a specific IDE, even = if it's a free one like Eclipse. OTOH, I think we can live with commits not being well-formatted and on= ly doing the formatting prior to tagging a release, right? If so, i.e= . we only require one formatting run prior to tagging a release, then = I'm fine with changing to the Eclipse formatter. Yoav Shapira Millennium Research Informatics >-----Original Message----- >From: Ceki G=FClc=FC [mailto:ceki@qos.ch] >Sent: Friday, September 03, 2004 8:33 AM >To: log4j-dev@logging.apache.org >Subject: [POLL] Source code formatting conventions > > >Hello all, > >We used to rely on jalopy as the indentation tool for log4j. For quit= e >a long time, the japoly plugin for eclipse did not run with version >3.0 of eclipse. This was a show stopper for many developers, includin= g >myself. It appears that the japoly plugin now supports eclipse >3.0. However, Eclipse 3.0 has built-in support for advanced code >formatting and indentation. > >With jalopy we are not constrained to use Eclipse in order to format >source code. Japoly has support for an Ant task which can format whol= e >directories, now just a single file. Japoly also supports other IDEs >such as JBuilder, JDeveloper, jEdit or NetBeans. But do we need to >format whole directories or do we need support for JBuilder? I tend t= o >think that the answer is no. > > >Build-in Eclipse formatting support: > >Advantages: > built-in support > >Disadvantages: > dependent on Eclipse 3.0 > > >Jalopy: >Advantages: > we already use it >Disadvantages: > requires the installation of Jalopy > real development *seems* to have shifted to a propriety alternativ= e > > >How does Eclipse formatting compare with Japoly? Should we consider >switching to Eclipse 3.0 formatting and abandon Jalopy? > > >-- >Ceki G=FClc=FC > > For log4j documentation consider "The complete log4j manual" > ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp > > > >---------------------------------------------------------------------= >To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org >For additional commands, e-mail: log4j-dev-help@logging.apache.org This e-mail, including any attachments, is a confidential business com= munication, and may contain information that is confidential, propriet= ary and/or privileged. This e-mail is intended only for the individua= l(s) to whom it is addressed, and may not be saved, copied, printed, d= isclosed or used by anyone else. If you are not the(an) intended reci= pient, please immediately delete this e-mail from your computer system= and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-dev-help@logging.apache.org