|
| Re: Scope of refactoring operations? [message #161610 is a reply to message #161562] |
Fri, 28 May 2004 09:58   |
 Ilja Preuss
Messages: 105
Registered: July 2009 |
Senior Member |
|
|
Richard Anderson wrote:
> What is the default scope of a refactoring operation (file, project,
> package, workspace)?
Workspace.
> Is there any way to control the scope?
Besides closing projects you don't want to be affected, or temporarily cut
dependencies between projects, nothing I am aware of.
> More specifically, if I use the Refactor / Change Method Signature,
> does the change affect the entire workspace?
Yes, sort of - of course only projects depending on the project the
refactoring is done in can be affected.
Why would you want to restrict the refactoring?
Cheers, Ilja
|
|
|
| Re: Scope of refactoring operations? [message #161638 is a reply to message #161562] |
Fri, 28 May 2004 13:22 |
Eclipse User |
|
|
|
Originally posted by: akiezun.cuthis.mit.this.edu.andthis
Richard Anderson wrote:
> What is the default scope of a refactoring operation (file, project,
> package, workspace)? Is there any way to control the scope?
>
> More specifically, if I use the Refactor / Change Method Signature, does
> the change affect the entire workspace?
>
the scope of that one is: all files that refer to that method or any
methods that this one is overridden by (from where it goes and find
appropriate methods up and down the hierarchy - recursively. which is
known as the 'ripple effect')
simpler put: unless the method is private or package visible, it
searches in the current project and all projects that depend on this one
(it makes you start the refactoring for a method that does not override
any methods)
cheers
a.
|
|
|
Powered by
FUDForum. Page generated in 0.03053 seconds
] 
Search
Help
Register
Login
Home
