Summary: | [move method] A behavior preserving transformation (Move Method Refactoring) is rejected due to conflicts of method names | ||
---|---|---|---|
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.3 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | stalebug |
Description
Melina Mongiovi
2014-05-14 13:29:06 EDT
*** Bug 434881 has been marked as a duplicate of this bug. *** (In reply to Melina Mongiovi from comment #0) > 4. Another refactoring tool applies the same transformation and the > resulting program (the program below) preserves the program behavior. > private long m(B b, int a) { > return 0; > } > } FYI: Moving the private method and leave it private would be useless. 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. 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. |