Project: JDT
Bug 75432 Pull up refactoring leaves unused imports
Reported: 2004-10-01 03:46:47 | Status: closed fixed

After using the pull up refactoring on a method, the method is removed from the sub class and put into the super class, but the sub class still has unused imports from before the refactoring. Can the refactoring be enhanced in a way that the imports of the sub class are organized after the refactoring?

Files changed in fix:
org.eclipse.jdt.ui.tests.refactoring/resources/PullUp/test12/out/B.java org.eclipse.jdt.ui.tests.refactoring/resources/PullUp/test4/out/B.java org.eclipse.jdt.ui.tests.refactoring/resources/PullUp/testGenerics12/out/B.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/PullUpTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/HierarchyRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/PullUpRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/PushDownRefactoring.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/PullUpWizard.java