Community
Participate
Working Groups
Eclipse rejects a rename class refactoring. The transformation could be performed with an additional change. Steps: 1. Create the classes: package p1; public class A { } package p1; import p2.*; public class B extends A { } package p2; import p1.*; public class C extends A { } 2. Apply the rename class to rename A to C. Eclipse will show an error: Another type named C is referenced in C.java. Other refactoring tools perform the following behavior-preserving transformation: package p1; public class C { } package p1; import p2.*; public class B extends C { } package p2; import p1.*; public class C extends p1.C { }
Moving to JDT/UI
*** This bug has been marked as a duplicate of bug 391710 ***
(In reply to Markus Keller from comment #2) > > *** This bug has been marked as a duplicate of bug 391710 *** Why do you consider this bug as duplicate of bug 391710? In this bug, Eclipse rejects the transformation and reports the warning message: " Another type named * is referenced in *.", while in the bug 391710 Eclipse rejects the transformation and reports the message: "Name conflict with type *.". Therefore, for each transformation (this bug and bug 391710) a different precondition was unsatisfied. In my point of view each bug is related to a different overly strong condition.