Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 178741

Summary:	Opening a copied workspace yields spurrious 'File Changed' dialog box while the splash is still active
Product:	[Eclipse Project] Platform	Reporter:	Maxime Daniel <maxime_daniel>
Component:	Resources	Assignee:	Platform-Resources-Inbox <platform-resources-inbox>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.3
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Maxime Daniel

2007-03-22 04:39:42 EDT

I20070320-0010

Scenario:
- open a brand new workspace /workspaces/t1;
- import org.eclipse.core.filesystem as source plugin;
- open EFS.java;
- close Eclipse;
- copy the workspace recursively onto a new directory /workspaces/t2 (used cp -r);
- open Eclipse upon /workspaces/t2;
- get a 'File Changed' dialog; the initialization will not resume until you 
  press one of its buttons.

I understand that the copy changes the file's date and that the cache contents will mismatch this. However, this is not a true change of the file. Comparing file contents might be expensive, but could be the way to go (at least when this allows to cancel a false alarm at a reasonable cost). Else, the message should be postponed to after the workbench has shown up (else the user won't have a clue of which file is involved - the file name does not appear, and the 'normal' clue, that is the file which is being edited, is not available at that time).

Comment 1 Maxime Daniel

2007-03-22 04:49:46 EDT

My first search did not bring it up... But another one did. Sorry for the noise.

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