Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "OJB Developers List" <ojb-dev@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Code Cleanup
Date: Wed, 17 Aug 2005 16:54:50 -0400
Message-ID: <41C2B90B26CA6343A75BF031D9A44E12D7982A@ODNEXCH2.em.ohio.gov>
Thread-Topic: Code Cleanup
Thread-Index: AcWjbOhiHB/JFWNoTyC+VIHaUv2koQAAJhJw
From: "Clute, Andrew" <Andrew.Clute@etech.ohio.gov>
To: "OJB Developers List" <ojb-dev@db.apache.org>


> Please don't. I don't think we agree on a coding standard (at=20
> least we would have to have a vote for it IMO). And applying=20
> it makes using CVS merging more difficult (esp. with local changes).
>=20

http://db.apache.org/ojb/code-standards.html

Is this no longer applicable?

For Eclipse users right now, what are you doing for code formatting? Are
you not doing it at all when inside your OJB project in eclipse? I know
that I am so use to using it for my normal work, that it is a hard-habit
to break when inside of OJB -- so much that I figured more than just me
had the same issue, and it would be nice to have a consistent settings.

However, the last thing I want to do is cause more work in the merge
process -- that is always a pain. So I will defer this until further
feedback is given.

-Andrew


---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org