[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mylar-dev] jira query synchronization and others
|
Eugene,
The reason for this weirdness is because we need to send a start date
that is relative to the server (not a calculated date based on the
local pc's time). If we try to use a local date inevitably we don't
have the time zone or the local clock is out of sync with the servers
which causes missed incomings. So we need a valid time stamp from the
repository for this to work.
Unfortunately, bugzilla doesn't return a timestamp equivalent of the
actual query execution time (the NOW) so we've implemented the work
around you see with getting the time stamp from the most recently
changed task returned.
It isn't pretty but works. If I've overlook a better solution to this
problem please let me know! :)
-Rob
On 2/1/07, Eugene Kuleshov <eu@xxxxxxxx> wrote:
Rob, Mik,
Can one of you look at the
RepositorySynchronizationManager.GetChangedTasksJob.run()
I don't understand the logic of that thing. For instance, why does it
only sets the last repository sync time only if there was changed tasks?
And also, why it is using the mostRecentTimeStamp from the changed tasks?
The problem is that mostRecentTimeStamp is in "who knows what"
timezone and for JIRA connector we can't construct reliable offset from
the current date.
So, I think that repository setSyncTime() should be set based on the
local timestamp and it should be also set when there is no updated tasks.
regards,
Eugene
_______________________________________________
mylar-dev mailing list
mylar-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mylar-dev
--
Robert Elves
Mylar committer, http://eclipse.org/mylar
