Bug 233712 - [rename] method so that it overrides ignores that visibility must not be reduced
Summary: [rename] method so that it overrides ignores that visibility must not be reduced
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
: 313041 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-05-23 12:34 EDT by Friedrich Steimann CLA
Modified: 2022-07-17 04:10 EDT (History)
3 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 Friedrich Steimann CLA 2008-05-23 12:34:30 EDT 
Build ID: Build ID: M20071023-1652

Steps To Reproduce:

public class A {
	public void m(Object o) {}
	void n() {
		m("abc");
	}
}

public class B extends A {
	void n(Object o) {}
}

Renaming n in B to m causes an error since visibility of m cannot be reduced in subclass.

More information:
Comment 1 Olivier Thomann CLA 2008-05-23 17:38:02 EDT 
Move to JDT/UI
Comment 2 Dani Megert CLA 2010-05-18 09:16:00 EDT 
*** Bug 313041 has been marked as a duplicate of this bug. ***
Comment 3 Eclipse Genie CLA 2020-06-25 20:02:56 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 2022-07-17 04:10:16 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.