Bugzilla – Full Text Bug Listing
| Summary: | [move method] move method cannot detect conflicting methods in parent classes. | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Jongwook Kim <jongwook.kim> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jongwook.kim, noopur_gupta |
| Version: | 3.8.1 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
In MoveInstanceMethodProcessor#checkConflictingMethod, we only consider the methods and constructors declared in that target type. All the methods (including the methods in its hierarchy) that are visible in the target type should be considered. 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. |
Here is an example. When A.m(String) is moved to class C via A.c, it conflicts with D.m(Object). The output is changed from "hello" to "bye" accordingly. class A { public static void main(String[] args) { new B().n(); } C c; void m(String s) { System.out.println("bye"); } } class B extends C { void n() { m("dummy"); } } class C extends D { } class D { void m(Object o) { System.out.println("hello"); } }