> * I would be +1 for a commons logging component
> that you would use by copying the source into
> each other component source tree *and* change the
> package names .... :-) (a template)
Well, technically you could do that with the proposed package (it was copied out of httpclient after all), but what is the point? Then if I want to write an adapater for "logging system foo", I need to repackage that adapter for each commons component I use it with (remember, we hope/expect most people to be using more than one commons component in their application). On top of being a hassle, that adds size to my application (for duplicate logging classes) and adds complexity (for the duplicate configuration).
