Community
Participate
Working Groups
1. Consider workspace/proj/src/test/com/a and workspace/proj/src/test/com/a If com.a is viwed in the PackageExplorer the View Hierarchy options works fine. If one goes the the Java Browsing perspective and selects the proj then "a" shows up in the packages, but the View Hierarchy option is unavailable. 2. In general, why can't one open the Hiearchy View on any aggregate: project, folder or package, or group of packages. (If one opens on a Project the results are bizarre-in my case I see mostly interfaces, and certainly not all classes).
Dani, can you please comment. I think that this is a problem of the virtual packages ? I opened feature request 103648 to support opening type hierarchy on multi selection.
The OpenTypeHierarchyAction does not handle LogicalPackage. This is a trivial fix once bug 103648 has been fixed.
I don't think part (1) of this bug depends on bug 103648. I interpret the paths from comment 0 as a copy-paste problem. The setup was meant like this: - source folder /proj/src/ with package com.a - source folder /proj/test/ with package com.a Opening the type hierarchy on the logical package for com.a does not work. But opening the type hierarchy on either of the two IPackageFragments shows the hierarchy of the (combined) package com.a, probably since type hierarchy computation is classpath-based and does not care about the physical structure. So, the OpenTypeHierarchyAction could just open the type hierarchy on any of the LogicalPackage's IPackageFragments.
yep, you're right.
Fixed in HEAD.
Verified in I20051213-0010.
