Summary: | Code Assist does not show methods if the return type is not on the classpath | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Alasdair Nottingham <alasdair.nottingham> |
Component: | Core | Assignee: | David Audel <david_audel> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 3.0 | ||
Target Milestone: | 3.0 M9 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Alasdair Nottingham
2003-11-21 09:19:49 EST
Please provide exact steps to reproduce. I have looked further into the problems I have been experiencing, and while I thought it was because I didn't have the class imported it was in fact because I did not have the class on the classpath. The steps needed to reproduce this are given below. The example given is simple, the more common one I come across is that the method I am calling throws an exception that extends another exception that I do not have on the classpath. In my environment I have projects for relativly small units of function, with interdependencies on each other. The real problem this introduces is when a project I depend on requires another one my project does not directly rely on but my project still needs to have it on its classpath. So steps to reproduce. Create Project A Create Class A in project A Create Project B Create Class B in project B Create method getA in class B that returns A Create Project C Setup class path in C so it references B, but not A Create Class C in project C Create method C in project C Attempt to use quick assist to put in a call to getA Code assist try to propose only correct code. If A is not inside classpath then a call to getA produce a compile error. So getA is not proposed. Work as designed. Closed. |