I believe the best course of action is to continue to support LogKit until Log4J 2.0 is released.
Feature freeze I suppose...
How many features have been added to LogKit recently?
However, in the mean time we should start putting together stronger support for Log4J in the Avalon containers. Many of our users will most likely be more willing to work with Log4J, and it will be one less issue to worry about.
Excellent. But from what I see in your post, there is no real thing that 1.3 will not have is the Logger.getLogger() issue "solved".
Question: how blocking is this WRT our immediate move to log4j 1.3?
Concidering that Log4J 1.3 is not released yet, very. We need it to be released. However we can make Log4J users more at home with our containers.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
