Project: JDT
Bug 76241 Inline method should refuse to work when calls to the method are ambiguous [refactoring] [inline method]
Reported: 2004-10-14 06:17:36 | Status: resolved fixed

I200410130800 Inlining one of the foo(...) methods of the first compilation unit below should refuse to work because the calls to foo(...) are ambiguous. Potential loss of work. public class A { protected void foo(String s) { System.out.println("A.foo()"); } protected void foo(Integer i) { System.out.println("A.foo()"); } } public class B1 extends A { public void bar1() { foo(null); } } public class B2 extends A { public void bar2() { foo(null); } }

Files changed in fix:
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/InlineMethodRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/TargetProvider.java