Bug 476293

Description Melina Mongiovi 2015-09-01 07:41:21 EDT

By applying a pull up method refactoring to move B.m to class A, it makes class A abstract (this bug I have already reported https://bugs.eclipse.org/bugs/show_bug.cgi?id=476256) and implements a new method in class C.
I know that without implementing method C.m, the resulting program does not compile. However, we do not know if the user wants to such implementation (probably not) and sometimes he is not aware of it, because it is not a local transformation.
I think the better decision is reporting a warning message to alloy the user choosing between make class C abstract or give up the transformation. If he wants to implement C.m, he does it manually and after that, applies the transformation.

Before Refactoring:

public class A {}
abstract class B extends A {
    public abstract int m(int a);
}
class C extends A {}

Resulting Program:

public abstract class A {
     public abstract int m(int a); 
}
abstract class B extends A {}
class C extends A {
	public int m(int a) {
		return 0;
	}
}