Summary: | [Pull Up field] A behavior preserving transformation (Pull Up Field Refactoring) is rejected. [Field 'p.C.x' declared in type 'p.C' has a different type than its moved counterpart] | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Melina Mongiovi <melmongiovi> |
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | daniel_megert |
Version: | 4.5 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Mac OS X | ||
Whiteboard: | stalebug |
Description
Melina Mongiovi
2016-11-16 09:39:15 EST
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. As of 4.12 M1 it is actually worse: The unnecessary error is shown and one can continue the refactoring which results in wrong code: it removes C.x! The error should be changed into a warning and the refactoring should generate: package p; class A { int x; } class B extends A { } class C extends A { boolean x; } 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. 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. |