On Dec 23, 2005, at 6:37 PM, Elias Ross wrote:
On Thu, 2005-12-22 at 00:46 -0600, Curt Arnold wrote:
I'd prefer to expedite the 2.0 branch and get log4j using a much
finer grained locking than maintaining two parallel sets of appenders
with different locking characteristics.
I'd be happy to help expedite a 2.0 release, but it seems ever further
away. And I anticipate (in six months) you'll find yourself in a
similarly unpleasant situation for 2.0 where people demand application
binary compatibility.
However, the big major version change and a namespace change would
clearly signal that there is no intention of being binary
compatible. I would think that we'd want, where reasonable, to
maintain logging statement and configuration compatibility as long as
you simply changed your import statements. It may be possible to
provide a shim that supports some log4j 1.x applications (log4j
users, not extenders) without recompiling by delegating to the log4j
2.0 classes.
It's also likely people are going to want both styles of
appenders. You
Joe Java coder might not understand (or want to learn about) read/
write
locking rules.
A good analogy is how the new JDK 1.5 java.util.concurrent.*
collection
classes did not deprecate existing locked collections classes, nor
were
java.util.Vector or java.util.Hashtable considered for removal.
The concurrent library I proposed is around 1000 lines of new
code/comments to maintain, compared to about 44,000 lines total for
the
existing log4j code base. Frankly, all I would like from the log4j is
an endorsement and place in svn, I can maintain and deal with the
implementation details.
I haven't taken a serious look at the code. But if all the IP issues
are addressed and there are no objections, I'd have no problem having
the contribution in the sandbox. If it then progresses to something
that the community wants in a formal log4j release, then all it would
take is a "svn mv" or two to graft in into the log4j source tree.
Hope you all have a wonderful Christmas. I'll be off the list for a
few days.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
