What I ended up doing these days...
I have the most basic logging interface in the package space of my
libraries
interface Console {
void println(String)
}
And if the application using that library wants to log what's going
on *inside* the library I inject a Console implementation being
whatever logger is being used. IMO makes it a very clear contract and
also makes you think about logging an not just log everything!
I know - no log level bla bla ...but it is simple and gets the job
done. And I would argue that a library should be so robust that (at
least preferably) it does not need any logging at all ...or if there
is a problem you just debug it.
IMO this also comes down to a question of API design.
My 2 cents
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
