Bugzilla – Full Text Bug Listing
| Summary: | [move method] binding of method call changes due to incomplete conflicting method check | ||
|---|---|---|---|
| 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: | 4.4.2 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
See MoveInstanceMethodProcessor#checkConflictingMethod. 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. |
After A.m(B) is moved to B, the binding of method call m() inside B.n() is changed from C.m() to B.m(). class A { void m(B b) { } } class B extends C { void n() { m(); } } class C { void m() { } } It occurs since JDT's conflicting method does not consider inheritance relationship.