Bug 296920 - [EditorMgmt] Exception when deleting project with open but not yet activated editors
Summary: [EditorMgmt] Exception when deleting project with open but not yet activated ...
Status: CLOSED DUPLICATE of bug 41431
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact: Remy Suen CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-04 10:21 EST by DMaliarevich CLA
Modified: 2009-12-16 02:56 EST (History)
1 user (show)

See Also:

Attachments
The exception stack trace has been uploaded. (21.08 KB, text/plain)
2009-12-04 10:24 EST, DMaliarevich CLA 		no flags Details
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 DMaliarevich CLA 2009-12-04 10:21:23 EST 
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; ru; rv:1.9.1.5) Gecko/20091109 Ubuntu/9.10 (karmic) Firefox/3.5.5
Build Identifier: M20090917-0800

Ther is an exception:
org.eclipse.core.runtime.CoreException: The file does not exist.

That happends when I delete project from Package Navigator (and from filesystem) after I've restarted the workspace with some java files from this project already opened in the java editor.


Reproducible: Always

Steps to Reproduce:
1. Create simple Java project.
2. Create some java classes in the source folded.
3. Open two or three java files it the editors
4. Choose from Restart from File menu (or close Eclipse and start it again)
5. Notice that java files are still opened in their editors. Do nothing with them.
6. Delete your java project: Choose "Delete" from Package Navigator popup menu, alse select a checkbox "Delete from filesystem..".
7. The project will be deleted.
8. Opened editors will be refreshed, and the exception will be thrown.
Comment 1 DMaliarevich CLA 2009-12-04 10:24:03 EST 
Created attachment 153819 [details]
The exception stack trace has been uploaded.

The exception stack trace has been uploaded.
Comment 2 Paul Webster CLA 2009-12-07 09:10:10 EST 
This problem seems familiar to me.  Might be the problem that we defer to the editor to close itself if its input closes, but the editors haven't been instantiated by us yet and so cannot react to the close.

PW
Comment 3 Remy Suen CLA 2009-12-07 09:27:56 EST 
There are several old bugs about this like bug 41431, bug 52279, and bug 101391. They mention the _closing_ of a project instead of a _deletion_ though. I suspect the root cause is identical though.
Comment 4 DMaliarevich CLA 2009-12-07 10:15:08 EST 
Yes, there are some familar bugs.

Note: if step #4 (restart eclipse) is skipped everything works fine: project gets deleted, all opened editors are closed.
Comment 5 Paul Webster CLA 2009-12-15 12:09:23 EST 
Remy, Do you want a 3.5.2 milestone?

PW
Comment 6 Remy Suen CLA 2009-12-15 12:18:33 EST 
(In reply to comment #5)
> Remy, Do you want a 3.5.2 milestone?

No plans at the moment.
Comment 7 Remy Suen CLA 2009-12-15 12:21:06 EST 
To be clear, this was not intended to be a 3.5.1 or 3.5.2 candidate. There was a mistake during triage where the 'Target Milestone' field was set to 3.5.1 when the intended field to change was the 'Version' field.

Our apologies for any confusion that this has caused.
Comment 8 Dani Megert CLA 2009-12-16 02:40:36 EST 

*** This bug has been marked as a duplicate of bug 29570 ***
Comment 9 Dani Megert CLA 2009-12-16 02:55:51 EST 

*** This bug has been marked as a duplicate of bug 41431 ***
Comment 10 Dani Megert CLA 2009-12-16 02:56:26 EST 
>*** This bug has been marked as a duplicate of bug 29570 ***
Actually not: the delete action should close the editors before deletion.