Community
Participate
Working Groups
We have a class called 'Module' which is in a custom package. Whenever we save a file and that file has compile errors Eclipse will remove the import of the custom Module class. I guess it thinks it's okay because java.lang.Module now exists and it's trying to fix the compile errors? We've tried everything we can think of to disable this "feature" but the alternative (disabling organize imports) is also very problematic. Eclipse should never automatically remove an import for a class that exists, even if there is an existing class in java.lang with the same name.
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.
