Community
Participate
Working Groups
I was able to see the problem in two ways: If use the 'Open Type Hierachy' by right clicking a type in an included library I do not see the descendants of that class from my own project. Note that there are up to three layers in between the root type and my derived classes, these are also from the libraries in use. However if I focus on one of the intermediate types then the types in my project appear. If I then return to the root types hierachy the 'discovered' types are there. I came across this problem programatically by calling. In this code snippet currentProject is of type IJavaProject : <snip> IType rootType = currentProject.findType(nameOfTheRootType); ITypeHierarchy typeHierarchy = rootType.newTypeHierarchy(new NullProgressMonitor()); IType[] classArray = typeHierarchy.getAllClasses(); </snip> In the returned array I did not find the classes in my project that I expected to see but did see the intermediate classes from the libraries I was using.
I confirm this behaviour. Ctrl+T and F4 open emtpy hierarchies. I haven't determined the exact method of "fixing" this, but it involves opening a subclass and then openening a hierarch on it.
We've fixed several problems in hierarchies recently. Can you please try with a recent integration build? If you still see the problem, could you add detailed steps to reproduce it to this bug report?
This is still happening in 200405180816. For instance, if I open the hierarchy on IWorkbench I get no children. If you perform this on any interface, you will only ever get interface children - never classes.
Kim this is a separate issue. I've entered bug 62686 for you.
Nigel, Travis, do you still see the problem in 3.0 RC1 ?
Nope. I checked RC1 yesterday and the one class that always had a problem is fine now.
Thanks. Please reopen if you see the problem again.
