Andrew Sykes wrote:
Wouldn't it be a good idea to just get stuck into moving the logging? I
assume it's got to go sometime. Or is there any special reason why
things have to be done in a specific order? If IIRC wraps log4j isn't
log4j already a dependency?
Avalon logger is only a service provided via an Interface.
Every avalon container supply its own implementation to the components
requiring the logger service.
The wrapper I referred is an implementation of the Logger service on top
of log4j, so that you don't need to change your code and you can use
log4j anyway.
We currently don't depend on log4j. I would prefer to add log4j only
when we will remove the whole avalon dependency (or we will provide our
own implementation of the avalon services).
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
