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

Bug 287803

Summary: [pull up][push down] should show be enabled for nested types
Product: [Eclipse Project] JDT Reporter: Raksha Vasisht <raksha.vasisht>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: markus.kell.r
Version: 3.5   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Raksha Vasisht CLA 2009-08-27 06:30:28 EDT
Build ID: M20090826-1100

Steps To Reproduce:
Build ID: M20090826-1100

Steps To Reproduce:
1.Testcase :
public class Foo {
	class abc {
		int x;

		void bar(int y) {
			x= y;

		}
	}

	class xyz extends abc {

	}

}
2. When the pull up/push down actions are invoked on the methods in the nested class it works fine. Here if the push down action is invoked on abc.bar() , the refactoring works fine, but the action is not activated in the context menu of the class itself, which should be since the behaviour should be uniform compared to the top-level class. (The actions are activated and work fine for class Foo and its methods)

3.Expected --> pull up /push down refactoring actions should be active in the context menu when nested type is selected.
Comment 1 Markus Keller CLA 2009-08-27 06:43:10 EDT
In addition to enabling the actions in the context menu, they should also *work* when a nested type is selected. When I currently invoke them from the main menu, I only get an error dialog (whose text should probably also be updated).
Comment 2 Eclipse Genie CLA 2020-03-22 16:40:09 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.