Bug 473924 - [refactoring] Remove Method Parameter Refactoring results in compilation error
Summary: [refactoring] Remove Method Parameter Refactoring results in compilation error
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.6   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-30 09:04 EDT by Melina Mongiovi CLA
Modified: 2023-02-05 17:14 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Melina Mongiovi CLA 2015-07-30 09:04:35 EDT 
Removing the method parameter of A.m(int) results in compilation error.

Before Refactoring:

public abstract class A {
    public abstract void m(int a);
}
class B extends A {
    public void m(int a) {}    
}

abstract class C extends A {
    public int m() {
        return 10;
    }    
}

Resulting Program:

public abstract class A {
    public abstract void m();
}
class B extends A {
    public void m() {}    
}

abstract class C extends A {
    public int m() {
        return 10;
    }    
}
Comment 1 Eclipse Genie CLA 2018-12-06 12:44:15 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.
Comment 2 Dani Megert CLA 2018-12-10 12:14:24 EST 
Still an issue using 4.10.
Comment 3 Eclipse Genie CLA 2020-11-30 05:29:45 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.
Comment 4 Jeff Johnston CLA 2020-11-30 18:14:57 EST 
Problem still exists in 2020-12 RC1
Comment 5 Eclipse Genie CLA 2023-02-05 17:14:03 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.