Bugzilla – Full Text Bug Listing
| Summary: | [rename] Renaming a member type should check for shadowing of member type in superclass | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Max Schaefer <xiemaisi> |
| Component: | UI | Assignee: | Markus Keller <markus.kell.r> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | martinae |
| Version: | 3.3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| 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 ID: M20071023-1652 Steps To Reproduce: Test case: abstract class MyMap implements Map { abstract static class MyEntry implements Entry { } } Renaming the member class MyEntry to Entry yields abstract class MyMap implements Map { abstract static class Entry implements Entry { } } which does not compile. It is possible to construct examples where the resulting code would still compile, but have a different behaviour. More information: