Bug 39311 - Outliner did not refresh after method rename (refactor)
Summary: Outliner did not refresh after method rename (refactor)
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M2   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-25 06:36 EDT by Philipe Mulet CLA
Modified: 2003-07-16 06:06 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 Philipe Mulet CLA 2003-06-25 06:36:56 EDT 
Build 20030611 + jdt/core v_359

Did change AstNode.toString(int) into AstNode.print(int) through refactor 
rename operation (from selection in editor). Outliner did not refresh, and was 
still showing old 'toString' method name.

When trying to further select the 'print' method in editor and perform a 
signature change refactoring, it complained that the method was no longer 
existing.
Comment 1 Jerome Lanneluc CLA 2003-06-25 07:03:17 EDT 
Reproduced by starting a self-hosting workspace, opening AstNode.java (only 
editor open), and doing the refactoring described above.
Comment 2 Jerome Lanneluc CLA 2003-06-25 09:22:57 EDT 
BufferCache was still using hasUnsavedChanges() instead of canBeRemovedFromCache
().

Fixed.
Comment 3 David Audel CLA 2003-07-16 06:06:17 EDT 
Verifid.