Community
Participate
Working Groups
Build ID: M20071023-1652 Steps To Reproduce: 1. Create a new plug-in project named 'test.core' with default settings. Ensure that the plug-in options 'Generate an activator' and 'This plug-in will make contributions to the UI' are turned on. 2. Create a second plug-in project name 'test.bundle' in the same way. 3. In the MANIFEST.MF of 'test.core', export the package of the activator class. In the same package, create an abstract class called AbstractActivator that extends AbstractUIPlugin. Update class Activator to extend AbstractActivator. 4. In the MANIFEST.MF of 'test.bundle', make it dependent on 'test.core'. Then update the Activator of 'test.bundle' to extend AbstractActivator from 'test.core'. 5. Select class Activator in 'test.core' in the Package Explorer and press F4 to get the Hierarchy View with that class. 6. In the Hierarchy View, select class AbstractUIPlugin and open its source code. Then press the 'Link with Editor' button in the Package Explorer. The selected type in the Package Explorer is in project 'test.bundle'. This is incorrect as class Activator in project 'test.core' cannot see any classes in project 'test.bundle'. More information:
I think that's because jdt.core shares all JAR's across projects. So it's more or less random which project is the parent of a JAR. Moving to jdt.core for comments.
Right, the hierarchy view shows the hierarchy on the entire workspace. So if a .jar is referenced twice, one is picked up randomly. Maybe we could use the one that has the same project as the focus of the hierarchy.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
