Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 81011 invoked from network); 23 Dec 2006 22:07:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Dec 2006 22:07:27 -0000 Received: (qmail 11317 invoked by uid 500); 23 Dec 2006 22:07:34 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 10721 invoked by uid 500); 23 Dec 2006 22:07:33 -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 10710 invoked by uid 99); 23 Dec 2006 22:07:33 -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 14:07:33 -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 alexei.zakharov@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 14:07:23 -0800 Received: by ug-out-1314.google.com with SMTP id z36so2678935uge for ; Sat, 23 Dec 2006 14:07:02 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JjOkZ1wGudal6n6szwkCXq3BX6wPw0gpd4UrOSe+2smIVN2fgsoXJZ+R+mmfuysQeHQZAOgT+pIfYA3C2uXKqQmeq68kOWKc32WbMJCbBAkixqycPjpRENU4imhQBSVd1g2NBolJiffzKKGwRKoQtZ+Vtuxp2lytBewbtO7AjJw= Received: by 10.78.164.13 with SMTP id m13mr1018853hue.1166911622319; Sat, 23 Dec 2006 14:07:02 -0800 (PST) Received: by 10.78.183.12 with HTTP; Sat, 23 Dec 2006 14:07:02 -0800 (PST) Message-ID: <2c9597b90612231407ifad4f87u607bd98733ab67f6@mail.gmail.com> Date: Sun, 24 Dec 2006 01:07:02 +0300 From: "Alexei Zakharov" To: dev@harmony.apache.org Subject: Re: [classlib][logging] format of log messages In-Reply-To: <458DA201.5030702@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2c9597b90612221632u2c23da3cs2f063b6752ce2c95@mail.gmail.com> <6784BD24-EE8C-4624-9DEE-09B6BF49E451@pobox.com> <458DA201.5030702@gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org I hope this won't be the reason of legal claims. I remember the discussion about the toString() method several months ago - do we allowed to use Sun's strings or not. Regards, 2006/12/24, Tim Ellison : > 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 > -- Alexei Zakharov, Intel ESSD