Unless there is a clear advantange to commons over the generalization Sacha did it is not worth the trouble to switch to an alternate logging wrapper.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Jason Dillon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 08, 2002 9:30 PM Subject: Re: [JBoss-dev] Design: Plans to decouple JBoss from log4j > The major issue with Log4j that I have is size... it is huge. Commons is > very small. If Log4j has a 20k footprint (or smaller) for client usage an > dprovided a simple method to disable logging, then I would see no need for > Commons Logging. > > Generally I am a pro-"just use log4j", but our own requirement for > org.jboss.logging.Logger (for TRACE, removing need for huge jars on client > and serialization) makes me wonder of the commons approache is really a > better solution... backed by Log4j of course. > > What were the specific CL issues you had witrh XDoclet? > > --jason ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
