Bugzilla – Full Text Bug Listing
| Summary: | [pull up] incorrect update of the pulled-up member's access modifier | ||
|---|---|---|---|
| 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 | ||
Reproducible in Eclipse 3.8.1 also. Visibility is changed only when class E in present in the given example. 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. |
Suppose the package-public method D.m() in package q is pulled up to class C in package p: -------------------- BEFORE -------------------- package q; class D extends p.C { void m() { } } -------------------- AFTER -------------------- package p; public class C { protected void m() { // m() becomes protected. } } class E { void n() { new D().m(); // ERROR: m() is not visible. } }