I've got to say... I have had nothing but problems with
commons-logging, especially with ant-driven tasks. There are so many
versions that invariably get loaded into the classloader (particularly
if you're using Tomcat taskdefs) and you end up getting classloader
errors because commons-logging is so stupidly picky about versioning
of the Logging class.
And has anybody ever actually hooked commons-logging up to something
other than Log4j? It's nice to be abstract, but the tradeoffs aren't
worth it to me. I'm -1.
On 9/18/05, Andrus Adamchik <andru..bjectstyle.org> wrote:
>
> On Sep 18, 2005, at 2:22 PM, Gili wrote:
>
> > You talk about removing log4j's jar from the client. How can
> > you do this without discarding all logging? If you run into a
> > logger.info("foo") won't it throw ClassNotFoundError?
>
> internals will be replaced by commons-logging - it is lighter and not
> that invasive as it can be configured to work with all major logging
> implementations... But no exposure of this in the method signatures
> either.
>
> Andrus
>
>
This archive was generated by hypermail 2.0.0 : Sun Sep 18 2005 - 15:01:12 EDT