Bug 39135 - Bad patterns in ISO8601DateFormat and DateTimeDateFormat
Summary: Bad patterns in ISO8601DateFormat and DateTimeDateFormat
Status: RESOLVED FIXED
Alias: None
Product: Log4j - Now in Jira
Classification: Unclassified
Component: Layout (show other bugs)
Version: 1.3alpha
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: log4j-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-28 19:38 UTC by Curt Arnold
Modified: 2006-03-28 11:49 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Curt Arnold 2006-03-28 19:38:52 UTC 
o.a.l.helpers.ISO8601DateFormat and o.a.l.helpers.DateTimeDateFormat were restored to the trunk in rev 
371710 on 2006-01-23 logged against bug 35452 (the catch all log4j 1.3 incompatibility bug).  These 
implementations were provided strictly for existing applications and are not used with log4j.  The new 
implementations simply delegate to java.util.SimpleDateFormat unlike the log4j 1.2 implementations 
which attempted an independent implementation.

Unfortunately, the patterns used were lifted directly from the log4j 1.2 javadoc comments which were 
wrong.  The use of YYYY instead of yyyy would result in an exception on construction and the use of yyyy-
mm-dd instead of yyyy-MM-dd would result in the value of the hour being used as the date.
Comment 1 Curt Arnold 2006-03-28 19:49:24 UTC 
Committed on trunk in rev 389572, 1.2 branch in rev 389573.