Here's a patch that removes CheapDateFormatter and makes the callers
use java.util.Date instead. CheapDateFormatter used to convert the
timestamps to GMT, whereas Date.toString() will use the local time
zone. Date.toString() also formats the timestamp differently. So,
where CheapDateFormatter produces a timestamp like
2010-08-18 11:38:59.755 GMT
we will now print something like this instead:
Wed Aug 18 13:38:59 CEST 2010
I think either one of these two formats works just as well as the
other for logging purposes, but others may disagree.
Full list of changes made by the patch:
Removed unused imports, including CheapDateFormatter. No actual use of
CheapDateFormatter in this class.
Use Date.toString() instead of CheapDateFormatter to format the
timestamp included in timeout exceptions when
derby.locks.deadlockTrace has been set.
Use Date.toString() to produce the timestamp in the log stream header.
Use Date.toString() instead of CheapDateFormatter when writing the
startup and shutdown messages to derby.log. Also removed unused
imports, including CheapDateFormatter.
Use Date instead of CheapDateFormatter when server prints console
Removed CheapDateFormatter class and its unit tests.
Filter out a line with a timestamp from derbyrunjartest since the
format of the timestamp has changed and isn't caught by the old