Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 317842 - If .target file is edited outside Eclipse, Target Editor opens empty
Summary: If .target file is edited outside Eclipse, Target Editor opens empty
Status: VERIFIED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 3.7 M5   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-24 11:17 EDT by Nick Boldt CLA
Modified: 2011-01-25 05:03 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Boldt CLA 2010-06-24 11:17:19 EDT
With Eclipse 3.6:

1. open some .target file in Target Editor; watch as PDE resolves it.

http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/m2e-e36.target

2. close editor; change file outside Eclipse (eg., reorder <unit> tags)

3. reopen file in Target Editor - now the editor is blank w/ no explanation that the file needs to be F5'd or File > Refresh'd.

(Aside: why can't Eclipse just refresh the file automatically? Since no editor will work on a non-up-to-date file, what's the point of waiting to refresh when the user MUST do so manually? What possible use case is there for making this behaviour (refreshing a file so it can be opened in Eclipse) optional?)
Comment 1 Curtis Windatt CLA 2010-06-24 12:01:30 EDT
Eclipse has a policy of not refreshing the contents of files automatically, though there is an option on the General > Workspace preference page to try and refresh automatically in the background.  See the discussion on bug 264196.

It would be better for the target editor to act like the other editors and tell the user that it is out of synch.  The functionality is part of platform text and is supported in the manifest editor, so it should be reasonably easy to hook it in to the target.  Marking for investigation in 3.7.
Comment 2 Dean Roberts CLA 2011-01-19 10:42:58 EST
Just confirmed that the fix for bug 331332 also fixes the problem described in this defect.

Should this defect be closed as resolved fixed?  (Not sure it is close enough to bug 331332 to be marked as duplicate)
Comment 3 Curtis Windatt CLA 2011-01-19 10:45:24 EST
Fixed in M5 by bug 331332.
Comment 4 Ankur Sharma CLA 2011-01-25 05:03:04 EST
Verified in I20110124-1800