Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: geronimo-dev@incubator.apache.org
Message-ID: <3F3CB3B9.8070200@gmx.de>
Date: Fri, 15 Aug 2003 12:19:37 +0200
From: Robert Stupp <snazy@gmx.de>
Reply-To: snazy@snazy.de
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20030725
MIME-Version: 1.0
To: geronimo-dev@incubator.apache.org
Subject: Re: coding conventions
References: <3F3CAC65.10700@sun.com>
In-Reply-To: <3F3CAC65.10700@sun.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Code formatting could be performed through a "plugin" on the server side
of CVS, which formats the Java code on each commit. So nobody would have
to take care of code formatting.

BTW: The code formatter (ctrl-shift-F) in Eclipse is fine and configurable.

Aditya Gore wrote:
| I am something of a newbie to open source...
| Was browsing through the code and came across many files
| that have lines that extend way beyond 80 characters. Cutting
| these into multiple lines could be a task in itself. Do such
| things qualify for a patch?
|
| thanks,
| :aditya
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/PLO5Kk+yu2LQ72QRApTYAJ9ACPQnS1JgB9NxGQ76dMUG4ldPjACgoM5o
+AnhiBg4S8jWq6ipYL4dG6E=
=5Aef
-----END PGP SIGNATURE-----