Comments on: Commons Logging Has To Die

by: Jonas Bonér » Blog Archive » Stay Out of Jar Hell with Jar Jar Links

Sat, 31 Dec 2005 09:33:58 +0000

[…] Remove unwanted dependencies Some days ago I blogged about the problem with Commons Logging and when software depends on it. Well, using Jar Jar, it is actually a simple matter to remove any unwanted dependency altogether. It might not always be the best solution, f.e. you might actually want to have some logging in place, not just use Commons Logging. But is some cases it is very convenient. (Please note that this feature is still experimental.) […]

by: Jonas Bonér » Stay Out of Jar Hell with Jar Jar Links

Fri, 09 Dec 2005 12:52:30 +0000

by: Yannick Menager

Wed, 30 Nov 2005 10:10:14 +0000

Another suggestion would be to use java.util.logging

The API is functional… The implementation is crap, but that’s not that difficult to replace ( or even write a layer that passes the logs to log4j, i’ve done that in the past )

by: toto

Mon, 28 Nov 2005 12:45:54 +0000

Agree. We really should get the dirt of programmers habits. Stop using Apache Commons-, they spread the shit like no others around. Avoid using JBoss-, you’ll get hooks all over your poor little POJOs. SUN Java APIs lacks a few things, but it’s generally largerly usable, and is far more fast and reliable than the dirt you’ll find googlising your implementation problems.

by: Stephan

Fri, 25 Nov 2005 07:30:49 +0000

Hey, you could start with a European clogging-exorcism at JavaPolis…. that was the only thing missing on our agenda

by: Michael Slattery

Fri, 25 Nov 2005 02:48:22 +0000

How about a new library that is API-compatible with commons logging (i.e. same class and package names) that is just a thin layer over log4j? I think it would be very easy to implement.

by: Eugene Kuleshov

Thu, 24 Nov 2005 22:10:24 +0000

By the way, Chris cheated in his JarJar-based logging remover. He basically replacing all the logging-related instructions with NOP/POP equivalents to consume stack. This is very easy to implement in ASM’s one-pass visitor, but it leaves all overhead of the string concatenation and severity level checking in the code.

A better way would be to cut off all the instructions that produce arguments for logging method calls. Bug me about it if you are interested to know how to do that.

by: Bob Lee

Thu, 24 Nov 2005 20:08:22 +0000

Thank you! There’s no point in Commons logging. An API to decouple you from an API which is supposed to decouple you from your logging implementation? It seems like you should write adapters between log4j and java.util.logging in the form of Appenders/Handlers, right?

by: Jonas

Thu, 24 Nov 2005 18:54:48 +0000

Dion,

Hehe. I was actually thinking of using a bit of dry Swedish sarcasm. But since people don’t seem to get that, and so many still think that Commons Logging is a good idea (it is from Apache after all… hmmm…perhaps a bit of sarcasm there… ), I decided to be angry instead.

But I really enjoyed your post when I read it. You know I like your British sense of humor.

by: Jonas

Thu, 24 Nov 2005 18:51:25 +0000

Hani, clogging-exorcism seems to be something I just can not miss, please let me know when you are planning on getting together