Project: JDT
Bug 190982 [introduce parameter object] clean up refactoring activation code
Reported: 2007-06-05 04:52:13 | Status: resolved fixed

I20070605-0010 The code in RefactoringExecutionStarter.startIntroduceParameterObject(IMethod, Shell) does too much work outside of the refactoring. We should move the initialization code from IntroduceParameterObjectRefactoring's constructor to checkInitialConditions(..) and just abort with fatal RefactoringStatus.

Files changed in fix:
org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/IntroduceParameterObjectTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/ParameterInfo.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/TypeContextChecker.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/ChangeSignatureRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/IntroduceParameterObjectRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/ParameterObjectFactory.java