Evolution of Logging in Java

Slalom Consultant Brett Hovenkotter

Slalom Consultant Brett Hovenkotter has extensive experience as a Development Team Lead across a broad range of methodologies, technologies and architectures.

When I first started doing development in Java back in 2000, there wasn’t a free logging framework available (at least not that I was aware of) so my development team wrote our own. Building a robust logging framework is not a trivial task, and thankfully Ceki Gülcü stepped up with log4j which was hosted by Apache and reached 1.0 in January 2001.

Java eventually got an official logging API in version 1.4 a year later, but as is common with features that make their way into the SDK, it was too late and less robust than what the open source community had already come up with.

The diversity in logging implementations was a headache for the growing population of libraries and frameworks, most of which wanted to contribute to log messages. The solution was the Apache Commons Logging API that provided a simple Façade that would detect which logger was being used and direct log messages to it.

For years I used these tools for logging without ever considering looking elsewhere, but recently a colleague introduced me to Read more of this post


Get every new post delivered to your Inbox.

Join 130 other followers

%d bloggers like this: