commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig R. McClanahan" <craig...@apache.org>
Subject RE: [VOTE] Logging 1.0 Release (again)
Date Wed, 20 Feb 2002 01:27:08 GMT


On Tue, 19 Feb 2002, Steve Downey wrote:

> Date: Tue, 19 Feb 2002 20:07:35 -0500
> From: Steve Downey <steve.downey@netfolio.com>
> Reply-To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
> To: 'Jakarta Commons Developers List' <commons-dev@jakarta.apache.org>
> Subject: RE: [VOTE] Logging 1.0 Release (again)
>
> -1 as long as LogSource uses catch(Throwable){}
>
> It is far too risky in server side code to catch all thrown exceptions and
> errors.
>
> SWALLOWING them to boot is unforgivable.
>

Steve,

One thing to note is that LogSource is deprecated, and only there for
backwards compatibility for modules that depended on the prerelease
version.

Craig


>
> > -----Original Message-----
> > From: Craig R. McClanahan [mailto:craigmcc@apache.org]
> > Sent: Tuesday, February 19, 2002 7:56 PM
> > To: commons-dev@jakarta.apache.org
> > Subject: [VOTE] Logging 1.0 Release (again)
> >
> >
> > OK, the round of discussion last time around has triggered some
> > improvements in the pluggability of the Logging API.  In
> > particular, it is
> > now possible to plug your own factory class for Log instances, if you
> > don't want to use the default algorithm.  (For backwards
> > compatibility,
> > the default algorithm implements the logic that was in
> > LogSource -- which
> > is now deprecated but remains for API compatibility reasons).
> >
> > There are a number of suggested changes that are *not* included, and I
> > propose that we continue to not include them:
> > * Adding a generic "Level" concept (either as a unique class or
> >   as a set of integer constants) to the Log interface.
> > * Adding a log(Level, String) method to the Log interface.
> > * Adding mechanisms to configure loggers through the Log interface.
> >
> > Going down the path of implementing any of these in the
> > commons logging
> > wrapper would violate the principle on which this API was designed, of
> > being a very thin facade over the facilities of multiple underlying
> > wrapper implementations.
> >
> > Therefore, I propose the current code base (as currently
> > available in the
> > 20020219 nightly build) to be released as Commons Logging 1.0.  I
> > volunteer to act as release manager, and will follow the
> > standard Commons
> > release procedure as documented at:
> >
> >   http://jakarta.apache.org/commons/releases.html
> >
> >
> >
> >
> > ----- Cut Here -----
> > I vote as follows on the proposed Commons Logging 1.0 Release:
> > [ ] +1 - I support this release and am willing to help
> > [ ] +0 - I support this release, but cannot assist
> > [ ] -0 - I don't support this release
> > [ ] -1 - I vote against this release (requires valid *technical*
> >          reasoning)
> > ----- Cut Here -----
> >
> > Craig McClanahan
> >
> >
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail:
> > <mailto:commons-dev-help@jakarta.apache.org>
> >
>
> --
> To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>
>
>


--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message