Bug 172679 - Can't navigate hierarchy of binary type
Summary: Can't navigate hierarchy of binary type
Status: RESOLVED DUPLICATE of bug 73957
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-02 11:04 EST by Nick Edgar CLA
Modified: 2007-02-02 11:46 EST (History)
2 users (show)

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 Nick Edgar CLA 2007-02-02 11:04:54 EST 
3.3 M4

- with a project loaded that depends on org.eclipse.jface.databinding
- open type on SpinnerObservableValue
- press F4
- the Hierarchy view shows only SpinnerObservableValue, not the whole hierarchy
- back in the editor, select a reference to an inherited method, e.g. fireValueChange, and press F3
- it has no effect other than status line showing: Current text selection does not resolve to a Java element
Comment 1 Nick Edgar CLA 2007-02-02 11:11:34 EST 
May be a PDE classpath issue.
Comment 2 Markus Keller CLA 2007-02-02 11:29:33 EST 
Do you have bug 172633 in your log?
Comment 3 Markus Keller CLA 2007-02-02 11:39:46 EST 
Reproduced in M4 without an exception with steps from bug 172633 comment 3.

The problem is that the class file cannot be compiled. The ASTView shows an error at "... extends _AbstractSWTObservableValue_ {...":

The type org.eclipse.core.databinding.observable.value.AbstractObservableValue cannot be resolved. It is indirectly referenced from required .class files
Comment 4 Markus Keller CLA 2007-02-02 11:46:58 EST 
I think this is another dup of bug 73957.

Wassim, I guess you're the one who understands this problem best. Could you please adjust the summary of bug 73957 and add a comment explaining a workaround?
AFAIK, only importing all dependencies as binary really helps.

*** This bug has been marked as a duplicate of bug 73957 ***