| Summary: | [push down] Pushing down method leads to compilation error: The method M from the type T is not visible | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Gustavo Soares <gsoares> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | daniel_megert, deepakazad |
| Version: | 3.6 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
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. |
Build Identifier: 20090920-1017 Pushing down a method from a class to another in a different package may lead to a compilation error due to accessibility. Reproducible: Always Steps to Reproduce: 1. Create the classes: package p1; public class A { public long m(){ return new A().k(); } protected long k( ){ return 1; } } package p2; import p1.A; public class B extends A { } 2. Apply the push down refactoring to A.m: package p1; public class A { protected long k( ){ return 1; } } package p2; import p1.A; public class B extends A { public long m(){ return new A().k(); } } 3. After the refactoring the method k is not visible to the expression new A().k() in p1.B leading to compilation error.