Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <43F3B73E.4050402@amberpoint.com>
Date: Wed, 15 Feb 2006 15:20:30 -0800
From: Bryan Pendleton <bpendleton@amberpoint.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: [jira] Commented: (DERBY-515) Network Server should log server
 start and shutdown time to derby.log
References: <1133741133.1140042670496.JavaMail.jira@ajax.apache.org>
In-Reply-To: <1133741133.1140042670496.JavaMail.jira@ajax.apache.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

 > I chose GMT to keep it consistent with what is used for Derby boot message.

Sounds good.

 > About using xxxxxxFILTERED-VERSION-NUMBERxxxxxx, I did'nt see other tests
 > doing it. I saw the current pattern in tests is to add master files with
 > version number to release/build.xml file. I would like to know what
 > problems you see if there are more files in this list.

Sorry, I shouldn't have introduced this red herring. I was remembering
the discussion of a few weeks ago:
http://www.nabble.com/forum/ViewPost.jtp?post=2342175&framed=y
in which there were a bunch of problems due to having release-specific
values in test output, and so I was sort of inventing a new mechanism
on the spot to see if it helped.

But I don't think it does; I think you should stick with the implementation
in your current patch proposal.

So, bottom line: thumbs up from me on your patch, and thanks for answering
my questions!

thanks,

bryan