Leif Mortenson wrote:
> Berin Loritsch wrote:
>
>> jean-pierre lerbscher wrote:
>>
>>> Hi,
>>> It seems that these classes (ExcaliburComponentManager,
>>> AbstractLoggable,... ) depends on org.apache.log.Logger class and
>>> org.apache.avalon.excalibur.logger.LogKitManager deprecated interface.
>>> Could you do something for the next release ?
>>> Thanks
>>> JPL
>>
>>
>>
>>
>> These are freshly deprecated interfaces, let's give other projects that
>> use Excalibur time to migrate first. You'd be surprised how long this
>> actually takes.
>
>
> It looks like the LogKitManager was replaced by LoggerManager, but what
> was ExcaliburComponentManager replaced by? Could you explain how things
> should be done now?
>
ExcaliburComponentManager Must generate deprecation warnings because it
*must* support the legacy Loggable interface. Do NOT change that, please.
You will piss off *alot* of users.
The Loggable interface is freshly deprecated, we cannot simply drop it from
the face of the earth.
ExcaliburComponentManager and friends are *not* deprecated. Using them will
definitely cause deprecation warnings in the interim, but that is the price
to pay for backwards compatibility.
I am still working on the replacement technology--I am alot closer than I
was, but still not all the way there yet. Once done with the ContainerManager
and friends, if we are happy with that, we can talk about deprecating the
ECM and friends.
P.S. The LogKitManager is required by ECM to provide LogKit Logger interfaces
to the Loggable components. Please do not break that. It would cause more
problems than it is worth.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
