Bug 395349

Summary: [rename] Renaming a method inherited from both generic interface and class does not rename method in interface
Product: [Eclipse Project] JDT Reporter: Milos Gligoric <milos.gligoric>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: ASSIGNED --- QA Contact:
Severity: normal    
Priority: P3 CC: deepakazad, markus.kell.r, nikolaymetchev
Version: 4.2.1   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard: stalebug
Bug Depends on: 99622    
Bug Blocks:    

Description Milos Gligoric CLA 2012-11-29 00:08:13 EST
Steps to reproduce:
1. Invoke "Rename" as indicated in code below
2. The resulting file does not compile ("The type RenameMethodBug1.A must implement the inherited abstract method I1<Object>.f(Object)")

class RenameMethodBug1 extends C3 {
    class A extends C<Object> implements I1<Object> {
        // Invoke "Rename" on 'f'
        public void f(Object o) {
        }
    }
}

class C3 {
    class C<E> { // <<< This type parameter has to be different from
                 // the one in Interface I1
        public void f(E e) {
        }
    }
}

interface I1<T> {
    void f(T t);
}

(Thanks to Yilong Li for helping with the bug report.)
Comment 1 Deepak Azad CLA 2012-12-01 00:30:15 EST
I suspect this is very similar to bug 377146.
Comment 2 Nikolay Metchev CLA 2014-05-14 08:36:46 EDT
The patch in bug 99622 fixes this problem
Comment 3 Eclipse Genie CLA 2020-06-12 18:18:13 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.

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.
Comment 4 Eclipse Genie CLA 2023-01-24 03:45:08 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.