[ http://issues.apache.org/jira/browse/DERBY-515?page=comments#action_12366554 ]
Deepa Remesh commented on DERBY-515: ------------------------------------ Thanks Bryan for looking at the patch. I chose GMT to keep it consistent with what is used for Derby boot message. The network server start and shutdown messages get printed along with derby boot messages in derby.log. Something like this: Apache Derby Network Server - 10.2.0.0 alpha started and ready to accept connections on port 1527 at 2006-02-15 21:43:13.252 GMT ---------------------------------------------------------------- 2006-02-15 21:44:07.871 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.2.0.0 alpha - (1): instance c013800d-0109-6faa-b988-00000015dbe8 on database directory C:\deepa\Derby\derby_testing\nwserver\testdb Database Class Loader started - derby.database.classpath='' Apache Derby Network Server - 10.2.0.0 alpha shutdown at 2006-02-15 21:47:02.772 GMT If we are using local time, I think we should do it for all messages to keep it consistent in derby.log. 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. > Network Server should log server start and shutdown time to derby.log > --------------------------------------------------------------------- > > Key: DERBY-515 > URL: http://issues.apache.org/jira/browse/DERBY-515 > Project: Derby > Type: Improvement > Components: Network Server > Versions: 10.1.2.0, 10.2.0.0 > Reporter: Kathey Marsden > Assignee: Deepa Remesh > Fix For: 10.2.0.0 > Attachments: derby-515-v2.diff, derby-515-v2.status > > Network server currently only reports the start and stop of network server to > the console output and does not print an associated timestamp. > It would be helpful if the start and stop times of network server were > recorded in the derby.log, so there would not be a need to check t the > console output. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
