Bug 137960 - [pull up] should not allow moving static method to interface [refactoring]
Summary: [pull up] should not allow moving static method to interface [refactoring]
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-21 11:09 EDT by Markus Keller CLA
Modified: 2018-11-18 18:50 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2006-04-21 11:09:26 EDT
N20060421-0010

interface I {
}
class A implements I {
    public static void pullUp() {
    }
}

PullUp of a static method into an interface always result in a compile error and is of no use. I cannot imagine a situation where the user really wants to change a static method into a nonstatic interface method.

Currently the error message only tells about 'changed program semantics'. The refactoring should either gray out static methods when an interface is selected as target, or it should stop with a fatal error.
Comment 1 Noopur Gupta CLA 2014-08-05 08:12:19 EDT
In Java 8, the pull up refactoring should move the static method to the destination interface (as a static interface method).
Comment 2 Eclipse Genie CLA 2018-11-18 18:50:22 EST
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.

If you have further information on the current state of the bug, please add it. 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.