Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 84848 invoked from network); 29 Jan 2002 20:07:43 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 29 Jan 2002 20:07:43 -0000 Received: (qmail 23193 invoked by uid 97); 29 Jan 2002 20:07:46 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 23176 invoked by uid 97); 29 Jan 2002 20:07:45 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 23165 invoked from network); 29 Jan 2002 20:07:45 -0000 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: [Logging] [VOTE] Commons Logging 1.0 Release Content-Transfer-Encoding: quoted-printable Date: Tue, 29 Jan 2002 12:02:40 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: <458473676F1AC74A84EAB2F22004DA6D1B1F02@mail.nextance.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Logging] [VOTE] Commons Logging 1.0 Release Thread-Index: AcGo/QZP5mTOQvQmQJmc9QsQJdtxkgAAT7Rg From: "Scott Sanders" To: "Jakarta Commons Developers List" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Inline. > -----Original Message----- > From: Craig R. McClanahan [mailto:craigmcc@apache.org]=20 > Sent: Tuesday, January 29, 2002 11:46 AM > To: Jakarta Commons Developers List > Subject: RE: [Logging] [VOTE] Commons Logging 1.0 Release >=20 > On Tue, 29 Jan 2002, Scott Sanders wrote: >=20 > > Date: Tue, 29 Jan 2002 11:27:23 -0800 > > From: Scott Sanders > > Reply-To: Jakarta Commons Developers List=20 > > > > To: Jakarta Commons Developers List > > Subject: RE: [Logging] [VOTE] Commons Logging 1.0 Release > > > > Berin, I think that I understand how you feel, and although the=20 > > abstraction was implemented outside of Avalon, I do believe that=20 > > Avalon should be attributed in some way, because it ended=20 > up being so=20 > > close. > > >=20 > If you read back through the COMMONS-DEV discussions, I'd say=20 > that the commons logging API started out closer to Log4j than=20 > it did to LogKit, and during the development sycle morphed=20 > towards what was obviously a good idea :-). I am looking into this now. I think that this is the proper impl, which is why the Avalon and commons are so close. >=20 > I'm absolutely +1 on attribution, though, as long as its to=20 > both of them. I would agree. Wasn't Ceki also involved when he created Log4jME? >=20 > > What can we do to make this better? The biggest difference=20 > that I see=20 > > is that commons-logging is trying to be super small. I=20 > want to talk=20 > > this out before I give my +1 on the release. I am willing=20 > to try and=20 > > make this better. > > >=20 > In particular, commons-logging *only* wants to be a facade=20 > (rather than providing anything other than a basic System.out=20 > logging implementation itself), where LogKit's white paper=20 > explicitly describes the Avalon team's need to go beyond that. +1 Of course they are both influenced by Log4j AND Avalon. >=20 > I'm glad there is more than one choice in logging frameworks=20 > in the world, with differing feature sets and philosophies. =20 > I just want to avoid having a Commons component that wants to=20 > do logging (such as Digester or > BeanUtils) dictating to an application that it *must* use=20 > exactly one of them, whether it wants to or not. That should=20 > be the choice of the developer who is using the commons=20 > components, or the sysadmin deploying the application into a=20 > production environment already based on one of them. Yes. >=20 > > I am -0 until I can see completely where Berin is coming from. > > > > Scott Sanders > > >=20 > Craig >=20 >=20 > > > -----Original Message----- > > > From: Berin Loritsch [mailto:bloritsch@apache.org] > > > Sent: Tuesday, January 29, 2002 11:28 AM > > > To: Jakarta Commons Developers List > > > Subject: Re: [Logging] [VOTE] Commons Logging 1.0 Release > > > > > > > > > Craig R. McClanahan wrote: > > > > > > > We've refined the commons-logging APIs, and documented the > > > mechanics. > > > > In addition, I've heard from numerous people on various > > > projects that > > > > would like to use these APIs, but are hesitant to do so > > > without a 1.0 > > > > release. > > > > > > > > Therefore, I'd like to now propose that we do a 1.0=20 > release of the=20 > > > > commons-logging package, based on the current contents=20 > of the CVS=20 > > > > repository for this package. I will volunteer to act=20 > as release=20 > > > > manager, following the standard process for Commons packages: > > > > > > > > http://jakarta.apache.org/commons/releases.html > > > > > > > > ----- CUT HERE ----- > > > > [ ] +1 I support the release of Commons Logging 1.0 and > > > will help [ ] > > > > +0 I support the release, but cannot help [ ] -0 I am not > > > in favor > > > > of the release [ ] -1 I am opposed to this release, and here's=20 > > > > why (attach reasons) > > > > ----- CUT HERE ----- > > > > > > > > > -1 > > > > > > > > > How many logger abstractions do we need? Avalon has a perfectly=20 > > > good one. (I am not a committer on commons though...). > > > > > > It looks like a direct rip off of the Avalon logger=20 > abstraction, and=20 > > > despite the work that Peter Donald and I put into it, we get no=20 > > > mention. > > > > > > > > > > > > > > > -- > > > > > > "They that give up essential liberty to obtain a little temporary=20 > > > safety > > > deserve neither liberty nor safety." > > > - Benjamin Franklin > > > > > > > > > -- > > > To unsubscribe, e-mail: > > > unsubscribe@jakarta.apache.org> > > > For > > > additional commands, > > > e-mail: > > > > > > > > > > -- > > To unsubscribe, e-mail: =20 > unsubscribe@jakarta.apache.org> > > For=20 > additional commands,=20 > e-mail:=20 > > > > > > >=20 >=20 >=20 > -- > To unsubscribe, e-mail: =20 > unsubscribe@jakarta.apache.org> > For=20 > additional commands,=20 > e-mail: >=20 >=20 -- To unsubscribe, e-mail: For additional commands, e-mail: