Community
Participate
Working Groups
Created attachment 90518 [details] A project that demonstrates the problem. Build ID: M20071023-1652 Steps To Reproduce: Put the following interfaces in separate files in a new project. Clean the project. Hilarity ensues. interface A extends Iterable<B> {} interface B extends C {} inteface C extends A {} More information: The compiler reports the following two errors: Cycle detected: a cycle exists in the type hierarchy between B and C The hierarchy of the type C is inconsistent This problem is dependent on the order of compilation. If the classes are renamed so that they compile in a different order, the problem disappears.
I've tried this case with a recent build and it works fine. Please try this case on a more recent build to see if you still detect a problem.
Was able to reproduce in 3.3.2 but it works fine in the latest 3.4 build. Closing as works for me. Do not believe we'll be doing a 3.3.3 build.
Verified for 3.4M6 using build I20080324-1300: problem not reproduced