CODEWITHSUNDEEP
eclipse
Tobber
Tobber

Reputation: 7541

Make eclipse remove unused imports but keep unresolved

Is there a way to make Eclipse keep used but unresolved imports?

I'm using Eclipse's save actions to remove unused imports. Unfortunately it also removes imports that are used, but not unresolved.

In the example below, eclipse will remove GeneratedClass, if I save MyClass before generating the GeneratedClass. When I late generate the code, MyClass will be missing the import.

import a.b.GeneratedClass;
public class MyClass extend GeneratedClass {}

Upvotes: 5

Views: 2491

Answers (3)

Tobber
Tobber

Reputation: 7541

Thanks to Bananeweizen and Krispy for their contributions, but so far it seems that the answer to this question is No.

The most efficient work around for me, is just to hit ctrl+z every time I save a file with unresolved imports.

I have submitted a bug to Eclipse's bugtracker: https://bugs.eclipse.org/bugs/show_bug.cgi?id=395538

This Eclipse bug tracks this issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=357795

Upvotes: 4

Bananeweizen
Bananeweizen

Reputation: 22080

You can disable the clean up action and instead remove the unwanted imports manually one by one using Ctrl1 to invoke the quick fix for that.

Nevertheless you are just trying to hide the real problem. The real problem is that your generated code is not generated at the right time. You should fix that. If you don't know how to automatically involve actions in Eclipse during every project build, please look at this example (which automatically creates a jar file with a custom script during every build). You can have those builders applied to the project in any order that you want, so you can always have your code generation invoked automatically before the Java compiler, on saving your Java files.

Upvotes: 0

Krispy
Krispy

Reputation: 1108

Don't use the save macros and instead hit Ctrl-Shift-O which will give you more explicit control over when the imports should be tidied up.

Upvotes: 0

Related Questions