There has been some discussion over what the Logger interface should or should not be for the next release. I want input from the different projects that _use_ Avalon, or would like to use it to help us make the final decision.
First, let it be known that Avalon will allways prefer LogKit as the standard Logger--although it can provide hooks for you to add your own logger implementations. That is what the vote is for. There are a proposed Logger interface and Loggable interface. We have two choices to allow for pluggable Logger implementations: 1) Simply replace the Loggable and AbstractLoggable classes with the proposed version. This causes a backwards incompatibility, and is not preffered. 2) Deprecate Loggable and create a new interface to avoid incompatibilities. This causes us to have to use a less than desirable interface name for the equivalent of Loggable. Please be advised that the changes would affect you in two ways: The origin of the Logger interface is now org.apache.avalon.logger.Logger, and if we alter the interface name for Loggable, you would have to implement that interface instead. The actual client API for Logger and Abstract Logger will not change your existing code. The most impact will be for people who actually use the Loggable interface directly or place the logger in a local variable. You should be able to change the import statement for the Logger object and all will be working again. It is generally agreed that pluggable loggers would be a good thing for Avalon, and we should be able to provide support for Log4J and LogKit relatively easily. Committers, please place your votes. Users, please give your comments. Vote for approach 1 or 2 above. If you choose method 2, please provide a suggested name for the new interface. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
