Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 74238 invoked from network); 23 Dec 2006 21:39:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Dec 2006 21:39:57 -0000 Received: (qmail 64162 invoked by uid 500); 23 Dec 2006 21:39:51 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 64121 invoked by uid 500); 23 Dec 2006 21:39:51 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 64045 invoked by uid 99); 23 Dec 2006 21:39:50 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Dec 2006 13:39:50 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of t.p.ellison@gmail.com designates 66.249.92.174 as permitted sender) Received: from [66.249.92.174] (HELO ug-out-1314.google.com) (66.249.92.174) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Dec 2006 13:39:40 -0800 Received: by ug-out-1314.google.com with SMTP id z36so2676659uge for ; Sat, 23 Dec 2006 13:39:18 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=gDbhDpl8x/vIBdQfEnDgP4kYcnAhdq1tiM/jz9e4XrCOAPE4jTmxuokfSlkQ/mMGPMDrKXeUut/S2QdbEwqvCGy01+regLqZnw+M2rgBck1Rdn6/pvfDYK7kE1dB7TrEG7o70L1SgXnwhIPgLzSZ1RrBYq8RHM5UwNcQTEFuuRE= Received: by 10.67.22.7 with SMTP id z7mr15665270ugi.1166909958729; Sat, 23 Dec 2006 13:39:18 -0800 (PST) Received: from ?192.168.0.2? ( [86.111.176.100]) by mx.google.com with ESMTP id j3sm14810635ugd.2006.12.23.13.39.18; Sat, 23 Dec 2006 13:39:18 -0800 (PST) Message-ID: <458DA201.5030702@gmail.com> Date: Sat, 23 Dec 2006 21:39:13 +0000 From: Tim Ellison User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: dev@harmony.apache.org Subject: Re: [classlib][logging] format of log messages References: <2c9597b90612221632u2c23da3cs2f063b6752ce2c95@mail.gmail.com> <6784BD24-EE8C-4624-9DEE-09B6BF49E451@pobox.com> In-Reply-To: <6784BD24-EE8C-4624-9DEE-09B6BF49E451@pobox.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Geir Magnusson Jr. wrote: > > On Dec 22, 2006, at 7:32 PM, Alexei Zakharov wrote: > >> Hi, >> >> IMHO it is ok to use our own format for log messages produced by >> Logger.log() if the content is the same. BTW I like single-line style >> (currently used in Harmony) even more. So I think we can move this >> JIRA to non-bug-diff. What do others think? BTW I don't know any >> serious applications that do the log parsing. > > I can't tell you what apps do log parsing, but I think that we'd want to > reproduce the same format if possible. > > Maybe offer our format as an option? I think it is quite important that we *do* match the default format of a log message -- I think apps will expect it. Regards, Tim