robert burrell donkin wrote:
Log4JCategoryLog has been deprecated since 1.0.3. however, 1.0.2 is
still in wide circulation and that mean anyone who specifies
Log4JCategoryLog in a commons-logging.properties will find that the
latest jar is no longer a drop in substitution (since Log4JCategoryLog
has been removed from the distribution).
i wonder whether we might perhaps try to load Log4JLogger when
Log4JCategoryLog is specified but cannot be loaded. this would give
better backwards compatibility.
opinions?
Sounds like a wise move. Check the property to see if it matches the
deprecated class. If it does, issue a warning and use the replacement
class instead.
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
