Bug 3477 - No feedback when rename method is done on unsaved code (1GF5RIC)
Summary: No feedback when rename method is done on unsaved code (1GF5RIC)
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All Windows NT
: P4 normal (vote)
Target Milestone: ---   Edit
Assignee: Adam Kiezun CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:55 EDT by Dani Megert CLA
Modified: 2002-01-16 08:16 EST (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 Dani Megert CLA 2001-10-10 22:55:48 EDT 
Rename of a method that has already been changed
	but not saved, gives no feedback:

	1. Open SimpleTest
	2. In the editor change suite() to suites() - DO NOT SAVE
	3. Select suites in the outline and perform the rename refactoring (to xxx)
	4. Choose not to save the cu
	5. Press next
	==> no error, no warning, the window that shows the upcoming changes is empty


NOTES:
Comment 1 Martin Aeschlimann CLA 2001-10-16 11:16:01 EDT 
moved to 'active'
Comment 2 Adam Kiezun CLA 2001-10-18 06:24:24 EDT 
the problem is that the method is new and unsaved - so the indexer does not 
know about it. hence, no occurrences are found by the search engine, which 
results in no change object being created.
need to rethink the 'save before refactoring' policy.
Comment 3 DJ Houghton CLA 2001-10-24 07:10:12 EDT 
PRODUCT VERSION:
	0.122
Comment 4 Adam Kiezun CLA 2001-11-21 05:25:38 EST 
the user is now asked to save all dirty editors before performing this action.
which makes the problem disappear
20011120
Comment 5 Andre Weinand CLA 2002-01-16 08:16:23 EST 
Verified: 20020115 Dirty editors are automatically saved