Bugzilla – Full Text Bug Listing
| Summary: | Pull Up Method Refactoring makes a class abstract | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Melina Mongiovi <melmongiovi> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 4.6 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| 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. 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. |
Applying pull up method refactoring to move B.m to class A, makes A abstract. Making a class abstract may be not safe in some domains, such as, library (API) developments. Even, in other domains, the developer may not want to make a class abstract. I think at least Eclipse should report a message to alloy the user choosing between make a class abstract or give up the transformation. Before Refactoring: public class A {} abstract class B extends A { public abstract int m(int a); } Resulting Program: public abstract class A { public abstract int m(int a); } abstract class B extends A {}