Community
Participate
Working Groups
I have the following annotation: --------------------------------------------- package test; import static test.Annotation.E.X; public @interface Annotation { E e() default X; enum E { X, Y, Z; } } --------------------------------------------- I now choose to refactor -> move type to new file on the enum E. This produces the following invalid code, as the static import is left untouched: --------------------------------------------- package test; import static test.Annotation.E.X; public @interface Annotation { E e() default X; } --------------------------------------------- package test; public enum E { X, Y, Z; } --------------------------------------------- The expected output is: --------------------------------------------- package test; import static test.E.X; // Fix here public @interface Annotation { E e() default X; } --------------------------------------------- package test; public enum E { X, Y, Z; } ---------------------------------------------
This most likely belongs in the UI. Please move back if this is a problem in rewrite.
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.
*** Bug 561301 has been marked as a duplicate of this bug. ***
The issue still persists, see also: https://bugs.eclipse.org/bugs/show_bug.cgi?id=561301
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.
Bug still occurs in 4.23
