| Summary: | [move method] A behavior preserving transformation (Move Method Refactoring) is rejected using the API of Eclipse | ||
|---|---|---|---|
| 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.5 | ||
| 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. 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. |
Behavior Preserving Transformation is rejected. Reproducible: Always Steps to Reproduce: 1. Create the classes package p1; import p2.B; public class A { public static int m(B b){ return 0; } } package p2; public class B {} 2. Apply the move method refactoring to move method m from class A to class B. 3. Using the API of Eclipse, it does not apply the transformation and warns the following message: This refactoring cannot be used to move static methods. 4. Using the Graphical User Interface, we can apply it: package p1; public class A {} package p2; public class B { public static int m(){ return 0; } }