RE: java.util.concurrent

2006-06-01 Thread Patrick Linskey
> One suggestion for enforcing a code style is to use the > Checkstyle tool to actively enforce a style than to hope for > the best. It's over here: > > http://checkstyle.sourceforge.net/ > > Various projects use it, and it's pretty configurable. Apache doesn't provide any checkin hooks

Re: java.util.concurrent

2006-06-01 Thread Geir Magnusson Jr
There are, but I've never seen them used by an individual project and we're also careful about predictable load (although i wouldn't think this would be too bad). I assume though that anyone that is a committer would Do The Right Thing anyway... geir Patrick Linskey wrote: One suggestion

Re: java.util.concurrent

2006-06-01 Thread Geir Magnusson Jr
Abe White wrote: p.p.s. Not sure if Patrick has mentioned this, but the plan is to use a Sun-like coding style for OpenJPA. The code currently checked in uses the old SolarMetric style (which has its roots in the style of an even older company). So I just wanted to assure everyone that we'

Re: java.util.concurrent

2006-06-01 Thread Craig L Russell
Hi Abe, First, welcome to the OpenJPA mailing list. On May 31, 2006, at 6:36 PM, Abe White wrote: Hello all -- For those of you who don't know me, my name is Abe White, I'm a BEA employee (by way of SolarMetric), and I expect that I'll be spending most of my time working on OpenJPA once we

RE: java.util.concurrent

2006-06-01 Thread Patrick Linskey
> __ > > _ > > Notice: This email message, together with any attachments, may > > contain information of BEA Systems, Inc., its > subsidiaries and > > affiliated entities, that may be confidential, proprietary, > > co

Re: java.util.concurrent

2006-06-01 Thread Abe White
Doug Lea's original concurrency utils ( http://g.oswego.edu/dl/ classes/EDU/oswego/cs/dl/util/concurrent/intro.html ) are very good in jdk 1.4/1.3. Doug seems to recommend using the backport instead of his libs on the linked page, though.

Re: java.util.concurrent

2006-06-01 Thread Geir Magnusson Jr
Patrick Linskey wrote: >> __ >>> _ >>> Notice: This email message, together with any attachments, may >>> contain information of BEA Systems, Inc., its >> subsidiaries and >>> affiliated entities, that may be confident