Bug 207306 - WorkspaceSynchronizer does not handle deletion of a resource in certain circumstances
Summary: WorkspaceSynchronizer does not handle deletion of a resource in certain circu...
Status: VERIFIED FIXED
Alias: None
Product: EMF Services
Classification: Modeling
Component: Transaction (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 normal
Target Milestone: ---   Edit
Assignee: Christian Damus CLA
QA Contact:
URL:
Whiteboard:
Keywords: contributed
Depends on:
Blocks:
 
Reported: 2007-10-24 09:55 EDT by Geoff Martin CLA
Modified: 2017-02-24 15:10 EST (History)
1 user (show)

See Also:

Attachments
Patched class file (15.20 KB, patch)
2007-10-24 10:09 EDT, Geoff Martin CLA 		wayne.beaton: iplog+
Details | Diff
View All 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 Geoff Martin CLA 2007-10-24 09:55:13 EDT 
Build ID: I20070625-1500

Steps To Reproduce:
Create an unsaved EMF resource with error markers on the file then delete the resource. The WorkspaceListener will not detect the removal of the file.

More information:
The problem is that the WorkspaceListener inner class ignores all IResourceDelta's if they have the IResourceDelta.MARKERS flag set even if another change has happened.
Comment 1 Geoff Martin CLA 2007-10-24 10:09:36 EDT 
Created attachment 81061 [details]
Patched class file
Comment 2 Ed Merks CLA 2007-10-24 12:11:48 EDT 
This problem sounds just like https://bugs.eclipse.org/bugs/show_bug.cgi?id=205740  so the suggested solution likely works there too.  Thanks!
Comment 3 Christian Damus CLA 2007-10-25 00:04:32 EDT 
The attached fix is committed to CVS HEAD (1.2 branch).  Added a JUnit test to supplement the patch.

Note that the attachment was created not on the latest version of the file, but an earlier revision.
Comment 4 Christian Damus CLA 2007-10-25 14:37:44 EDT 
Fixed in the EMF TRANSACTION 1.2.0 I200710251346 build.
Comment 5 Nick Boldt CLA 2008-01-28 16:35:24 EST 
Move to verified as per bug 206558.
Comment 6 Christian Damus CLA 2008-02-28 11:58:16 EST 
Fix available in R1_1_maintenance: 1.1.2 (R200712061336).