Community
Participate
Working Groups
N20060411-0010 Type Hierarchy on Klass: ------------- interface Ints extends List<Integer> {} abstract class Klass implements List<String>, Ints {} ------------- In N20060407-0010, the supertypes of Klass were Object, Ints and List<E>. In N20060411-0010, the sypertypes are only Object and List<E>. I think the type hierarchy should not care about the validity of the supertypes' type arguments and always include all declared supertypes. This change broke our test ChangeTypeRefactoringTests.test4TypeParameters.
Created attachment 38408 [details] Proposed patch and regression test
Could you release the patch such that we can enable our test again?
+1 for 3.2RC2
Created attachment 39518 [details] Improved patch and regression tests
Released improved pacth and regression tests
*** Bug 136307 has been marked as a duplicate of this bug. ***
The fix in HEAD seems to fix only the type hierarchy, but not type bindings. In M6, getInterfaces() of the type binding for Klass returned: 0: java.util.List<java.lang.String> 1: xy.Ints , but with HEAD, I only get 0: java.util.List<java.lang.String> I would expect that both hierarchies are consistent. Shall I open a new bug or do you want to reopen this one? Our (disabled) test still fails.
If you're talking about the DOM AST ITypeBinding#getInterfaces(), yes please open a separate bug report.
Opened bug 138671 for comment 7.
Verified with I20060427-1600 for 3.2RC2