Mohsen Vakilian

The extract method refactoring generates an error if a method with the same signature as the extracted method already exists. But, it still lets the user perform the erroneous refactoring...

### The pull up refactoring on methods of inner classes could result in broken code If you pull up the method `m` from `C1` to `D1` in the following piece...

### Moving a method from an interface to a class generates a compilation error. If you move a method of an interface to a class, the refactoring will be performed...

### The Move refactoring doesn't handle a name conflict properly. If you move a Java class to a package that has a class with the same name, Eclipse pretends to...

### The configurations of refactorings performed via Quick Assist are not saved correctly. If you extract a method using quick assist, it will be serialized with the default name "extracted"...

### UDC does not capture the refactorings performed via Quick Assist correctly. UDC captures the invocation of quick assist but not the refactorings that are performed through the quick assist,...

### The pull up refactoring throws an NPE when pulling up a member that already exists in the superclass The Pull Up Refactoring has some problems when the same method...

### Eclipse doesn't log a move refactoring If you select the method `m2` in the following program and perform a move refactoring ("Refactor -> Move...") on it to move it...

### Eclipse logs rename compilation unit refactorings as rename type refactorings This bug report comes from issue #185. To reproduce this problem, perform the following steps. 1. Install a fresh...

### The Change Method Signature refactoring does not get recorded in refactoring histories correctly. The refactoring descriptor of Change Method Signature captured in `refactorings.history` doesn't capture the change in the...