Bug 724492 (BRMS-437) - Atom feeds display incorrect time from p.m. period
Summary: Atom feeds display incorrect time from p.m. period
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-437
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRM (Guvnor)
Version: 5.1.0.ER3
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: BRMS 5.2.0.GA
Assignee: Tihomir Surdilovic
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-10 21:34 UTC by Jiri Locker
Modified: 2011-08-15 05:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-01 13:26:56 UTC
Type: Bug

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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-437 0 None Closed Atom feeds display incorrect time from p.m. period 2011-09-16 08:18:48 UTC

Description Jiri Locker 2010-11-10 21:34:53 UTC 
securitylevel_name: Public

The feed (either for packege or a single artifact) displays the time of the last modification and the time when a comment was added. If the time is from the p.m. period (e.g. Modified on: Wed 10 Nov 2010 10:27:03 PM CET) the time in the feed is stored as
<updated>2010-11-10T10:27:03.882+01:00</updated> which is wrong (should be:
<updated>2010-11-10T22:27:03.882+01:00</updated>
Comment 1 Jiri Locker 2010-11-11 12:26:36 UTC 
Link: Added: This issue Cloned from JBQA-3766
Comment 2 Jiri Locker 2010-11-11 12:27:38 UTC 
Link: Removed: This issue Cloned from JBQA-3766
Comment 3 Jiri Locker 2010-11-11 12:27:56 UTC 
Link: Added: This issue is a dependency of JBQA-3766
Comment 4 Tihomir Surdilovic 2010-11-18 19:19:36 UTC 
This works as expected in trunk. Need to find out what change/jira fixed this.
Comment 5 lcarlon 2011-08-15 05:22:28 UTC 
Release notes not required as per https://issues.jboss.org/browse/BRMS-437
Note You need to log in before you can comment on or make changes to this bug.