I agree, seperate is better... One additional thing might be to have some packaging for the classes that are in the contrib directory... allowing them to be used and integrated... again, perhaps in another entirely seperate jar...
Rich -----Original Message----- From: Niclas Hedhman [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 12, 2002 9:12 PM To: Log4J Developers List Subject: Re: Log4J Log Viewer GUI (a la LogFactor5) On Thursday 12 December 2002 16:07, [EMAIL PROTECTED] wrote: > log4j-tools.jar that contains the clients/tools and removes them from the > log4j.jar? Or even in a jar per tool (log4j-chainsaw.jar, log4j-lf5.jar)? > Want to put that to a vote for making this change in v1.3? > > +1 > > Besides convienence, I always throught they should live in a separate jar. > A clean separation between base/required/server code and extended > tools/clients code. >From another random developer who enjoys log4j a lot.... Separate JAR files please, and startable with java -jar log4j-lf5.jar (or the 'double-click' if configured correctly in OS) would lower the threshold a lot... Niclas -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
