Bug 90114 - CVS/Team uses file creation time instead of modified time
Summary: CVS/Team uses file creation time instead of modified time
Status: RESOLVED DUPLICATE of bug 5337
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-03 11:53 EDT by Ryan Lowe CLA
Modified: 2005-04-03 19:46 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Lowe CLA 2005-04-03 11:53:01 EDT
In Eclipse 3.1M6:

After refreshing all projects in my workspace and then synchronizing with my CVS
repository, *most* of my projects' files have CVS decorations saying they have
been updated locally (>) when they clearly have not been.  The incorrectly
decorated files do not show up in the Team Synchronizing perspective.

I say *most* because there are a few which do not have the incorrect
decorations.  They seem to be files modified and checked back into CVS since I
upgraded to 3.1M6.

I can remove the false decorations by going to Preferences --> General -->
Appearance -- Label Decorations and unchecking "CVS" which is why I suspect this
a CVS/Team issue.

It also may be relevant that I used this workspace with Eclipse 3.1M5a and I
copied it to use it with 3.1 M6.  I will try using a new workspace location,
checking out my projects from CVS and see if that reproduces the problem as well.
Comment 1 Ryan Lowe CLA 2005-04-03 12:27:03 EDT
I created a new empty workspace and checked out my projects into it. I could not
reproduce this problem on a new workspace.
Comment 2 Ryan Lowe CLA 2005-04-03 12:40:23 EDT
I switched back from the new workspace (comment #1) to the imported workspace
(comment #0) from 3.1M5a, refreshed all projects and synchronized with the CVS
repository again.

This time all of the marked (>) files -- most of the files in my workspace --
show up in the Team Synchronization perspective as outgoing changes even though
I have not made changes to any of them, I have only switched workspaces.

Is this some sort of CVS/Team timestamping issue?  Is there a way to clear
CVS/Team timestamps to test that?

Could it be related to the Daylight Savings Time change?  The Windows machine
where I run Eclipse changed its time automatically last night and it seems that
the Linux machine (Fedora Core 3) I use as a CVS server changed automatically as
well.  Their time difference right now is only 20 seconds.
Comment 3 Ryan Lowe CLA 2005-04-03 13:02:36 EDT
I re-copied my 3.1M5a workspace to confirm I can reproduce this problem and I
can easily.  I will keep this 3.1M5a workspace and not change it.

This time I noticed that half of the CVS decorations (>) appeared during the
initial build after the workspace was imported into 3.1M6.  The rest of the
decorations appeared after I refreshed the projects.

After that I synchronized all of the projects with the CVS repository and all of
the marked files showed up in the Team Synchronization perspective.  None had
local changes.

---

Here's something interesting.  I copied the workspace with Windows Explorer so
strictly speaking all of the files are "new", just copies.  Here are timestamps
from a file in the workspace viewed from Windows Explorer:

In original 3.1M5 workspace:

Created: Wednesday, March 23, 2005, 4:57:18 AM
Modified: Wednesday, March 23, 2005, 4:59:44 AM

The same file, in copied 3.1M6 workspace:

Created: Today, April 03, 2005, 12:42:09 PM
Modified: Wednesday, March 23, 2005, 4:59:44 AM

That might explain why CVS/Team thinks this file has changed.

I have copied workspaces before and never had problems with Team Synchronization
like this.  Is this the intended behaviour?
Comment 4 Michael Valenta CLA 2005-04-03 19:46:43 EDT
The proble is actually in how Java determines the file timestamp on some file 
systems (e.g. FAT, Samba and a few others). The method that is used causes the 
timestamp to change when a time change occurs. The workaround is to either 
perform a Team>Update on all projects or a Clean imestamps in the synchronize 
view.

*** This bug has been marked as a duplicate of 5337 ***