329019 – Cannot open file in java editor after closing and reopening the project

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

Bug 329019 - Cannot open file in java editor after closing and reopening the project

Summary: Cannot open file in java editor after closing and reopening the project

Status:	CLOSED DUPLICATE of bug 41431

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	Text (show other bugs)
Version:	3.1
Hardware:	All All

Importance:	P3 minor (vote)
Target Milestone:	---
Assignee:	Platform-Text-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2010-10-29 05:13 EDT by Anshul
Modified:	2010-11-04 08:47 EDT (History)
CC List:	3 users (show)

See Also:

Attachments
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 Anshul

2010-10-29 05:13:43 EDT

Build Identifier: 3.6

resource doesnt refreshes when project is reopen

Reproducible: Always

Steps to Reproduce:
1.have 2 java files open in editor(one being active). 
2.restart eclipse as is
3. close the project
4. inactive file doesnt close and error message appears that Resource <filename> does not exists.
5. reopen the project and try opening the same inactive java file. File doesnt refresh and editor still shows the same error message

Comment 1 Remy Suen

2010-10-29 07:10:29 EDT

(In reply to comment #0)
> 5. reopen the project and try opening the same inactive java file. File doesnt
> refresh and editor still shows the same error message

If you manually refresh does the content show up?

Comment 2 Markus Keller

2010-11-04 06:56:34 EDT

The underlying problem in the platform is bug 18421.

Comment 3 Dani Megert

2010-11-04 08:47:39 EDT

(In reply to comment #2)
> The underlying problem in the platform is bug 18421.
Well, it all boils down to bug 41431: it's inconsistent that we close the activated editors but leave a stale one back.

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