Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368128 - In Kaliningrad timezone (Kaliningrad and Minsk) time of commit shows mistakenly
Summary: In Kaliningrad timezone (Kaliningrad and Minsk) time of commit shows mistakenly
Status: VERIFIED WORKSFORME
Alias: None
Product: Subversive
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Igor Burilo CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-09 04:46 EST by Igor Paikin CLA
Modified: 2013-11-22 06:37 EST (History)
2 users (show)

See Also:

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 Igor Paikin CLA 2012-01-09 04:46:26 EST 
Build Identifier: Eclipse for PHP Developers  Version: 3.0.2

After installing latest patches from Microsoft with new timezones:
WindowsXP-KB2570791-x86-RUS.exe
WindowsXP-KB2633952-x86-RUS.exe

Minsk and Kaliningrad are in new timezone +3 without DST (Daylight saving time).
In this timezone time of commit displays inproperly.

For example - datetime of commit in repository file: 
2012-01-08T12:33:02.092375Z

Displayed by eclipse:
08.01.12 8:03

If change timezone on local machine to any other (I've tried Nairobi, Moscow, GMT) time displayed OK.

TortoiseSVN also shows correct time of commut.


Reproducible: Always

Steps to Reproduce:
1. Install latest patches from MS to windows
2. Set timezone (GMT+03:00) Калиниград, Минск
3. In SVN repository perspective press "show history" on any file in repository
Comment 1 Alexander Gurov CLA 2012-12-27 11:42:18 EST 
I've tried to reproduce the situation with the steps provided and there were no problems. The only thing is that Eclipse IDE needs to be restarted after changing timezone in order to display time correctly (though don't know why, since Subversive does not use any static members for date/time operations).
Comment 2 Igor Paikin CLA 2013-11-22 03:29:45 EST 
(In reply to Alexander Gurov from comment #1)

This bug is reproducible in Java 1.6, on Java 1.7 - works fine.
Comment 3 Alexander Gurov CLA 2013-11-22 06:37:48 EST 
Thank you for informing regarding the situation.