Return-Path: Delivered-To: apmail-jakarta-log4j-dev-archive@apache.org Received: (qmail 41317 invoked from network); 12 Dec 2002 08:29:26 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 12 Dec 2002 08:29:26 -0000 Received: (qmail 23873 invoked by uid 97); 12 Dec 2002 08:30:45 -0000 Delivered-To: qmlist-jakarta-archive-log4j-dev@jakarta.apache.org Received: (qmail 23857 invoked by uid 97); 12 Dec 2002 08:30:44 -0000 Mailing-List: contact log4j-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@jakarta.apache.org Received: (qmail 23837 invoked by uid 98); 12 Dec 2002 08:30:44 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Subject: Antwort: RE: Log4J Log Viewer GUI (a la LogFactor5) To: "Log4J Developers List" X-Mailer: Lotus Notes Release 5.0.11 July 24, 2002 Message-ID: From: Ulrich.Kleeberger@witt-weiden.de Date: Thu, 12 Dec 2002 09:29:12 +0100 X-MIMETrack: Serialize by Router on domino/wen/Witt(Release 5.0.11 |July 24, 2002) at 12.12.2002 09:29:30 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N +1 for a jar per tool. uli An: "Log4J Developers List" Kopie: 12.12.02 09:07 Thema: RE: Log4J Log Viewer GUI (a la LogFactor5) Bitte antworten an "Log4J Developers List" > Alternatively you can develop LogViewer from within the log4j > project. You > will be given commit access (assuming a positive ballot) and > access to our > CVS repository. We could ship LogViewer with the log4j > distribution but in > a separate jar. I think that LF5 and Chainsaw should be handled similarly > especially as they do not seem to be actively maintained. 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. -Mark -- To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: