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

Bug 10604

Summary: Request New Refactorings: Inner Classes [refactoring]
Product: [Eclipse Project] JDT Reporter: David Corbin <dcorbin>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: RESOLVED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: dirk_baeumer
Version: 2.0Keywords: helpwanted
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description David Corbin CLA 2002-03-01 14:02:23 EST
Often, I end up with many utillity methods that only slightly related to the
main class.  I will frequently move these methods (if they're related) into a
named inner class (static).  Sometimes, after that, I will find that while those
methods should in fact be static in the main class, in this new Utility class,
they would be better server as instance methods, operating on a common field. 
In either one of these cases, I often move the Inner class to be an "outer
class".   I think all of these could be automated as:

1) "Move static Method to Inner Class" (create class if necessary)
2) "Convert class with all Static methods to Instance class" 
3) "Convert Inner Class to Outer Class"

It's possible that I'm entirely dreaming on #2.  I'll think about a bit more.
Comment 1 Erich Gamma CLA 2002-03-03 18:18:42 EST
should be considered after 2.0
Comment 2 Eric Nickell CLA 2002-06-11 16:25:02 EDT
Option #3 is related to Bug 6502.
Comment 3 Dirk Baeumer CLA 2002-07-23 09:01:39 EDT
No action planned for 2.1. PR is tagged as helpwanted.
Comment 4 Dirk Baeumer CLA 2003-04-28 06:03:11 EDT
Chaning state from assigned later to resolved later. Assigned later got 
introduced by the last bug conversion and is not a supported Eclipse bug state.
Comment 5 Denis Roy CLA 2009-08-30 02:13:06 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.