Community
Participate
Working Groups
Created attachment 206395 [details] Screenshot Please have a look at the attached screenshot. It's self-explaining.
- Can you check if this happens in the Type Hierarchy view as well ? (Select interface and press F4) - Is there anything in the error log?
(In reply to comment #1) > - Can you check if this happens in the Type Hierarchy view as well ? (Select > interface and press F4) > - Is there anything in the error log? Most likely bug 73957.
(In reply to comment #2) > Most likely bug 73957. Eike, can you confirm this? Or provide more info as requested in comment 0. At the moment, we do not have enough info to take any action.
(In reply to comment #1) > - Can you check if this happens in the Type Hierarchy view as well ? (Select > interface and press F4) Yes, in this regard the problem is "consistent". > - Is there anything in the error log? No, I checked it. There's nothing.
(In reply to comment #3) > (In reply to comment #2) > > Most likely bug 73957. > Eike, can you confirm this? I've looked at bug 73957 but it reads like a whole book and I fear I'm just too busy right now with customer work to study all the 76 comments on it ;-( > Or provide more info as requested in comment 0. You mean comment #2? Please see my comment #4 ;-) > At the moment, we do not have enough info to take any action. I fear there's nothing more I can provide now. In case it happens again, what should I check then?
(In reply to comment #5) > (In reply to comment #3) > > (In reply to comment #2) > > > Most likely bug 73957. > > Eike, can you confirm this? > > I've looked at bug 73957 but it reads like a whole book and I fear I'm just too > busy right now with customer work to study all the 76 comments on it ;-( > > > Or provide more info as requested in comment 0. > > You mean comment #2? Please see my comment #4 ;-) > > > At the moment, we do not have enough info to take any action. > > I fear there's nothing more I can provide now. In case it happens again, what > should I check then? Check whether the missing class is not inside a bundle that is directly required by one of the bundles you have in your workspace. Please reopen if you see this again.
That was a little quick :P As you could have seen in the screenshot I've attached the subtype that's missing from the type hierarchy is in the *same* file. There's basically this: class LocksChangedEvent implements CDOViewLocksChangedEvent {...} Opening te type hierarchy on the interface CDOViewLocksChangedEvent should list the implementing class LocksChangedEvent. But it does not.
(In reply to comment #7) > That was a little quick :P Look, we can't reproduce it and we can't do anything with this bug since it works for us. So, as long as you can't attach a demo workspace or steps that let us reproduce the problem there is nothing we can or will do. > As you could have seen in the screenshot I've attached the subtype that's > missing from the type hierarchy is in the *same* file. There's basically this: Mmh. Maybe you attached a wrong screenshot then. The one from comment 0 does not show that the types are declared in the same file.
Created attachment 207196 [details] Zipped workspace that reproduces the problem
In comment #9 I attached a zipped workspace that reproduces the problem. Steps to reproduce: - Install Eclipse SDK 3.8.0 (Build id: I20111027-1800) - Install EMF 2.8 into the target platform - Switch to the attached workspace - Open type org.eclipse.emf.internal.cdo.view.CDOViewImpl.LocksChangedEvent - Place caret on the implements clause (type CDOViewLocksChangedEvent) - Press CTRL+T or F4 You should now see the problem I've captured in the attached screenshot.
Thanks for the steps Eike! Deepak, please investigate.
Created attachment 208480 [details] Screenshot of another case Here I have another case of a "swallowed" sub type ;-(
Deepak, what did your analysis reveal? We just missed the first anniversary of this bug ;-(
I guess the problem is that CDOViewImpl contains more than 10 annotations. This makes it fall into the trap from bug 393192 comment 2. *** This bug has been marked as a duplicate of bug 393192 ***
I confirm that removing enough annotations (Java and Javadoc) made the type appear in the hierarchy. And I do have a package-info.java file in the containing package.
*** Bug 392171 has been marked as a duplicate of this bug. ***
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.
Will do. Will your fix end up in http://download.eclipse.org/eclipse/updates/3.8 ?
(In reply to comment #19) > Will do. Will your fix end up in > http://download.eclipse.org/eclipse/updates/3.8 ? Comment#18 was a request to Jesper the assignee of this bug. Of course you are welcome to verify the fix when it becomes available. The earlier GA version will be Kepler (4.3) and milestone M6.
I can confirm this as fixed by bug 393192, same pattern, but with the twist that in Eike's example, the package-info.java is the one from the package of the interface being investigated, not the editor's class. This confused me at first, since org.eclipse.emf.internal.cdo.view doesn't have a package-info.java. *** This bug has been marked as a duplicate of bug 393192 ***
Great! Thank you, guys. I'll try it out when the fix is available in 3.8.
Verified for build eclipse-SDK-I20130310-2000 M6.
