Community
Participate
Working Groups
Build ID: M20071023-1652 Steps To Reproduce: public class A { B b; private void m() {System.out.println("A");} void run() { b = new B(); b.m(); } public static void main(String args[]) { (new A()).run(); } } public class B extends A { public void m() {System.out.println("B");} } Using A instead of B changes declaration of b. This is fatal, since a refactoring should never change behaviour. More information: Appears to be the same problem as reported for generalize type: see http://bugs.eclipse.org/233437 (which includes more, less obvious examples).
Not a blocker, but a major bug.
Looks like the induhvidual who wrote SuperTypeConstraintsCreator.getOriginalMethods(..) reinvented the wheel but forgot to test the method modifiers. Should use helpers from Bindings, e.g. findOverriddenMethod(IMethodBinding, boolean).
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.
