Community
Participate
Working Groups
Consider this correct code: ----------------------------------------------------------------- package p1; import p2.C; public class C1 {} ----------------------------------------------------------------- package p2; public class C {} ----------------------------------------------------------------- Now, let's assume, I'm manually renaming C to C2 (i.e. not using the refactor -> rename operation) ----------------------------------------------------------------- package p2; public class C2 {} ----------------------------------------------------------------- Obviously, C1 now no longer compiles. I want to manually fix C1 using auto completion on the package name, so I put my cursor on "p2.C", hit Ctrl+Space and I get this ----------------------------------------------------------------- package p1; import p2.C2;; public class C1 {} ----------------------------------------------------------------- There is now an excess semi colon. Content assist should check if there already is a semi colon at the end of the import statement, and then not re-generate another one.
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.