Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335843 - [backport] [Filters] Renaming a project that contains resource filters fails.
Summary: [backport] [Filters] Renaming a project that contains resource filters fails.
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.6   Edit
Hardware: PC All
: P3 major (vote)
Target Milestone: 3.6.2   Edit
Assignee: Szymon Brandys CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 317824
Blocks:
  Show dependency tree
 
Reported: 2011-01-31 08:42 EST by Martin Oberhuber CLA
Modified: 2011-01-31 16:37 EST (History)
4 users (show)

See Also:
mober.at+eclipse: pmc_approved+
serge: review+

Attachments
Backport v01 (7.34 KB, patch)
2011-01-31 09:54 EST, Szymon Brandys CLA 		no flags 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 Martin Oberhuber CLA 2011-01-31 08:42:53 EST 
+++ This bug was initially created as a clone of Bug #317824 +++

CQ:WIND00253035 

Bug 317824 is a major problem when resource filters are used, since trying to rename a project results in an inconsistent workspace state leaving the user wondering what's going on.

We'll need a backport of this fix into the 3.6.x Stream for our product.
Comment 1 Szymon Brandys CLA 2011-01-31 08:50:59 EST 
Not sure. This bug is to backport Bug 317824 to 3.6.x, right?
Comment 2 Szymon Brandys CLA 2011-01-31 09:54:10 EST 
Created attachment 187963 [details]
Backport v01
Comment 3 Szymon Brandys CLA 2011-01-31 09:58:47 EST 
Versions of core.resources and core.tests.resources are already incremented.
Comment 4 Szymon Brandys CLA 2011-01-31 10:02:05 EST 
This is the same patch we applied to 3.7.
Comment 5 Serge Beauchamp CLA 2011-01-31 10:04:18 EST 
+1
Comment 6 Martin Oberhuber CLA 2011-01-31 10:14:56 EST 
+1 this fixes a serious issue, and the unmodified fix has been in use
   successfully since 3.7m2. I think the risk is minimal.
Comment 7 John Arthorne CLA 2011-01-31 13:40:23 EST 
My +1 not needed, but I think this is worth fixing despite it being very late.
Comment 8 Szymon Brandys CLA 2011-01-31 16:37:54 EST 
Fixed in the 3.6.x stream.