Hi, > One of the important features in 1.3 is that you no longer have to > ship log4j.jar in WARs. The idea is to place log4j.jar in your > server's common/lib or equivalent.
Some servers don't have a common/lib directory or equivalent. It's not part of the J2EE or Servlet Specifications, and as such it should not be a major design motivation. When people tell me "I put this and that in common/lib and now it's not working" I basically tell them to package their app as they should, in one WAR i.e. all libs in WEB-INF/lib. That's the only sustainable approach to portability. All that said, I'm 0 (neutral) on splitting log4j into its dependencies. I don't buy the argument that it's important to make the log4j jar small for either downloading or disk space. The latter especially is cheap. I do buy the easier develop/compile/test cycle argument that Niclas put forth. But I don't like JAR soup. What's I'd suggest is both (after all, this is easy to do with Ant): log4j.jar (just the core, which should include FileAppender and related), various add-ons e.g. SMTP, and then log4j-all.jar which is one jar containing the core and all the add-ons. Yoav --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
