You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by robert burrell donkin <ro...@blueyonder.co.uk> on 2006/01/25 20:06:00 UTC
[logging] compatibility with JCL 1.0.2
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?
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [logging] compatibility with JCL 1.0.2
Posted by Martin van den Bemt <ml...@mvdb.net>.
Sounds like a wise thing to do indeed, although you probably are a better judge of the issues that
may arise when not doing this..
Probably the fact that you wrote a mail about it, there must be a "doubt" and when in doubt, taking
the safe route is probably better..
Mvgr,
Martin
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?
>
> - robert
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [logging] compatibility with JCL 1.0.2
Posted by Dennis Lundberg <de...@apache.org>.
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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org