Community
Participate
Working Groups
Created attachment 222472 [details] Eclipse project to reproduce the bug Dear Eclipse users, members, and comitters, We are experiencing a "chaotique" functioning of the Type hierarchy indexing in Eclipse since 3.7 and even more with 4.2. Note that we never had this problem before. So we think this is bug. The problem is that sometimes when we have a class implementing an interface, pressing F4 on either the class or the interface will not show its supertype or its child class in the Hierarchy view. And the ctrl-T will neither work on a method declaration in the interface. I mentionned "chaotique" because it is only doing it for few classes. Our project contains dozens of other interfaces/classes for which the Hierarchy does work. However, it is always doing it for the same classes, so hopefully we were able to reproduce this bug. We isolated those classes, took out 99% of our project to clean this up, made a nice zip file, and attached it to this report. Normally, you should be able to reproduce this bug in your environment. Our environment is: - Eclipse Juno SR1 (Build id: 20121004-1855) - Using JDK 1.6.0_34 Optionaly: - This project used to be a web app running on a tomcat server 5.5. It's totally not workable/launchable has you have it here, but this is not the goal here. To see the bug: - Open the project in Eclipse - Goto the MyDAOImpl.java file - Press F4 -> You should see that the hierarchy window shows no parents, when there should be BaseDAOImpl and MyDAO - Same if you go in the MyDAO class Now the strange things: - Deleting the comments /** ... */ before the getC() function - or Deleting the getD() and getD2() functions - or Deleting the package-info.java will make the hierarchy work again ..... this looks really strange to us. I guess some others "actions" can make the hierarchy work again but I didn't find them all. In the case it is really a bug, hopefully they can help investigate on this. If you need any more details or have any remarks please don't hesitate to ask. Maxime
Looks like bug 362775. *** This bug has been marked as a duplicate of bug 362775 ***
*** This bug has been marked as a duplicate of bug 393192 ***
Jesper, Thanks for capturing this scenario in a junit test.
Please confirm this is indeed a duplicate of bug 393192 and that the issue is resolved. If there is something unique about the test case, we want to capture it as a junit.
This is exactly the same pattern as bug 393192: Java source file with: * More than 10 annotations * JavaDoc error which is suppressed * package-info.java present in class's package Just in case, I verified it against the committed fix in master, and it works now. Thanks for reporting! *** This bug has been marked as a duplicate of bug 393192 ***
Agreed and VERIFIED.