Community
Participate
Working Groups
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.
should be considered after 2.0
Option #3 is related to Bug 6502.
No action planned for 2.1. PR is tagged as helpwanted.
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.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.