Logging with Jakarta log4j - How to avoid depencies?

From: Jan van Mansum (jvm_at_nospam.com)
Date: 01/25/04 

Date: Sun, 25 Jan 2004 22:52:16 +0100

Hello group,

I have just been trying out the log4j library. As far as I understand
the idea is to keep the logging statements in your, even in the release
build. However, obviously you wouldn't want to have to ship the log4j
jar with your app, to avoid class definition not found exceptions. As
a matter of fact you wouldn't want the end user to be able to turn on
logging.

I have been thinking about how to handle this. The only thing I can
come up with so far, is just create a couple wrapper classes round the
log4j classes and replace them with empty onces at build-time.

Is this the only way to handle this problem? Has someone out there found
a more elegant way?

Thanks in advance,
regards,
Jan van Mansum.

Relevant Pages