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:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
