No problem at all; for compatibility reasons it makes sense to revert the change. Unico, do you know what change caused this?
I believe I am the guilty person :)
In the removal of LogKitManager / LogKitManageable, the sitemap no longer has a handle to the root LoggerManager, rather it just creates a LoggerManager based off of its current Logger.
This could probably be worked around by putting the LoggerManager that is passed to the Cocoon class into the ServiceManager, and thus any component that wants to get the 'root' LoggerManager for Cocoon can just do ServiceManager.lookup( LoggerManager.class.getName() );
-pete
