Quoting Elias Ross <[EMAIL PROTECTED]>: > > I would keep log4j.jar as-is (except maybe chainsaw) for easy > compatibility, then create a log4j-core.jar that has no appenders that > depend on third party software and then package these remaining > appenders in log4j-ext.jar (or log4j-smtp, jms, etc.) as you describe > below. >
I agree. For those who are going to use Log4j in an appserver, it would be annoying to gather all the variaous jars together. No matter what happens, there should be one jar (log4j.jar) that contains all of what Log4j consists of. Beyond that, I'm ok with whatever. Jake > > On Thu, 13 Jan 2005 18:08:43 +0100, Ceki Gülcü <[EMAIL PROTECTED]> wrote: > > > > > > Hello all, > > > > > > While performing some tests with Tomcat, I noticed that if log4j.jar > > > is placed in ./common/lib/, then for example an instance of > > > SMTAppender cannot be created without placing 'mail.jar' also in > > > ./common/lib/, placing 'mail.jar' in WEB-INF/lib is not enough. > > > > > > To circumvent this problem, I propose to split log4j.jar by > > > dependency. For example, > > > > > > log4j.jar (core classes depending only on JDK 1.2) > > > log4j-smtp.jar > > > log4j-jms.jar > > > log4j-db.jar > > > log4j-oro.jar > > > log4j-... > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
