Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 77302 - Undo of rename of CU/Type is not always rejected if file is dirty
Summary: Undo of rename of CU/Type is not always rejected if file is dirty
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: 3.1 M7   Edit
Assignee: Dirk Baeumer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-29 10:43 EDT by Dirk Baeumer CLA
Modified: 2005-05-10 12:46 EDT (History)
0 users

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 Dirk Baeumer CLA 2004-10-29 10:43:36 EDT 
I200410260800

- create a test file A with no implementations
- rename A to B
- go into B and make it dirty
- execute undo

Observe: the refactoring is undone.
Comment 1 Dirk Baeumer CLA 2005-04-28 19:06:05 EDT 
Got addressed with the new undo story.
Comment 2 Tom Hofmann CLA 2005-05-10 12:37:57 EDT 
verifying
Comment 3 Tom Hofmann CLA 2005-05-10 12:46:27 EDT 
verified that undoing the refactoring is correctly vetoed when executed from the
types view (or package explorer), as the editor has been dirtied after the
refactoring.

Undoing from the editor works via key-binding, but the menu entry is wrong.
Filed bug 94419.