Bug 34427 - Type hierarchy does not resolve for "Task"
Summary: Type hierarchy does not resolve for "Task"
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M1   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-10 14:55 EST by Darin Wright CLA
Modified: 2003-06-02 06:12 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darin Wright CLA 2003-03-10 14:55:52 EST 
In a self hosting workspace, I have the "org.apache.ant" plug-in loaded from 
the CVS repository. I used "Open Type" to open an editor 
on "org.apache.ant.tool.taskdefs.Task". I then selected the type in the 
outline, and chose "Open type hierarchy". The hierarchy opens, but is rooted 
at "Task" instead of "Object". Pressing "F3" on the supertype 
(ProjectComponent) results in a "beep". However, using "open type" I am able to 
open the type ProjectComponent.
Comment 1 Erich Gamma CLA 2003-03-17 06:11:24 EST 
Cannot reproduce, what is strange is that both types in the same JAR.

Discussed with Philippe this is unlikely a UI issue moving to JDT Core.

Darin do you have any additional info?
Comment 2 Darin Wright CLA 2003-03-17 09:58:19 EST 
It still does not work for me - but there is not really any more info. I will 
try a fresh workspace.
Comment 3 Darin Wright CLA 2003-03-17 10:05:58 EST 
Steps to reproduce (using build 20030313)
* start an empty workspace
* connect to repository dev.eclipse.org
* add "org.apache.ant" as project
* open "Task" with "Open Type" action
* select the super type in the editor, "ProjectComponent"
* hit F3 -> beep and error message "Current text selection doesn't resolve to a 
Java element".
Comment 4 Jerome Lanneluc CLA 2003-03-19 04:28:51 EST 
org.apache.ant doesn't have a JRE in its classpath. Thus the resolve aborts 
early. Nothing we can do here.

Is it ok to close?
Comment 5 Jerome Lanneluc CLA 2003-04-11 11:31:21 EDT 
Closing as invalid.