Bug 4041 - out of sync error message after copying resources (1GGR6VZ)
Summary: out of sync error message after copying resources (1GGR6VZ)
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 critical (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Kai-Uwe Maetzel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 23:05 EDT by Kai-Uwe Maetzel CLA
Modified: 2001-12-17 06:24 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kai-Uwe Maetzel CLA 2001-10-10 23:05:04 EDT
JLC (7/12/01 9:41:00 AM)
In the Java perspective:
1. create 1st project by: select File> New> Other> Micro Edition Examples> Microview - Checkers
2. create 2nd project by: select File> New> Other> Java Project
3. expand package com.ibm.ive.microview.examples.checkers in the 1st project
4. select copyright.txt and from the context menu select "copy" and then the 2nd project you created

Switch to the Resource perspective:
1. select the copyright.txt file that you copied to the 2nd project
2. from the context menu select delete

After confirming delete, you get the Delete Problems dialog:
Problems encountered while deleting resources.
when I select details I get:
Resource is out of sync with the file system: /test2/copyright.txt.

I can recreate this easily with Vame but not with Eclipse.  Also I only see this if I delete in the 
Resource perspective rather than in the Java perspective - I can get the error in the resource 
perspective and then switch back to the java perspective try the same thing and the file deletes.

NOTES:

LK (7/12/01 11:10:13 AM)
	This should be in the readme.  

AE (7/20/2001 2:48:37 PM)
	This has nothing to do with VAME, but seems a JDT problem to me.
	There are many situations where one runs into out of sync problems when moving, deleting, renaming,
	or even catching up, when Java projects are involved.
	My usual workaround is a sync with local followed by a rebuild all.
	Moved to ITPJUI.

KUM (8/6/2001 7:23:14 PM)
	Cannot reproduce in eclipse 128. Could you please outline the scenarios in which you get the out of sync
	messages when moving, deleting, etc.
Comment 1 DJ Houghton CLA 2001-10-24 07:28:41 EDT
PRODUCT VERSION:
VAME 2.0 Beta 0.4.6

Comment 2 Kai-Uwe Maetzel CLA 2001-12-17 06:24:45 EST
Closed. No scenario has been provided and following the given steps in build 
20011212 (eclipse) does not exhibit the described behavior.