Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 155521

Summary:	[reorg] Different move refactoring tools launched depending on variable visibility
Product:	[Eclipse Project] JDT	Reporter:	Max Gilead <max.gilead>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.3
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Max Gilead

2006-08-29 06:52:10 EDT

Different move refactoring tools are launched depending on variable visibility. It's textual move (huh?) for private variables and regular move eg. for public static variables. IMHO it's obvious that if user wants to move private variable to another class it either has to be made static with adjusted visibility (if no target class instance is available in context) or member variable with adjusted visibility (if target class instance is available in context). Are there any other possibilities? Please note that I'm not sure if the latter is automatically doable; maybe it always has to be static.

Comment 1 Martin Aeschlimann

2006-08-31 10:30:04 EDT

Move static fields is a refactoring. Move instance fields just a textual move.
I agree that this is a bit confusing, it would be good if the dialog indicates this better.

I son't think it is possible to offer a refactoring 'instance to static fields'.

We'll have a look at all moves in 3.3, there are several open gaps there.

Comment 2 Eclipse Genie

2020-04-20 06:33:14 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.