Bug 142995 - [refactoring] should allow to specify the scope for reference updating [introduce indirection][inline]
Summary: [refactoring] should allow to specify the scope for reference updating [intro...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Markus Keller CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-22 10:22 EDT by Tom Hofmann CLA
Modified: 2006-06-20 11:11 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Hofmann CLA 2006-05-22 10:22:12 EDT
3.2

- have a class with a couple of calls to System.arraycopy
- you would like to wrap all these calls to add index checking
- select Refactor > Create Indirection
- select "redirect all method invocations"
- click 'Preview'

> takes forever, as all calls to System.arraycopy in the workspace are collected
> clearing "redirect all method invocations" will only replace one single call

-> What I really want in this case is to just redirect the calls in my cu.
-> Need a way to specify the scope of the refactoring
Perhaps better using over "extract method"?
Comment 1 Markus Keller CLA 2006-06-08 06:12:01 EDT
Scope selection would probably look the same as in Java search dialog page.
Comment 2 Markus Keller CLA 2006-06-20 11:11:35 EDT
This would make sense for all refactorings that support partial updates (code still compiles with only some references updated).

For some refactorings, this is even state dependent, e.g. rename method would support a scope iff "Keep original method as delegate..." is checked.