Project: JDT
Bug 100846 [refactoring] Change method signature does not disallow changing implementations of binary methods
Reported: 2005-06-20 11:13:42 | Status: verified fixed

3.1 RC3 Steps to reproduce: - Create compilation unit class MyList extends ArrayList { public String toString() { return super.toString(); } } - Add parameter to MyList#toString() -> CMS does not complain, causing a semantic change -> During the computation of the method ripple, the refactoring should generate an error status as soon as a binary declaration occurs in the ripple -> This problem probably affects all refactoring clients of RippleMethodFinder (2)

Files changed in fix:
org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/ChangeSignatureTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/RefactoringCoreMessages.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/IntroduceParameterRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/ChangeSignatureRefactoring.java