Paul Kinnucan <[EMAIL PROTECTED]> writes: > Based on this experiment, I believe that JDEE 2.3.4 handles the test > case that you presented correctly within its limitations, i.e., that > it only imports and completes things that are on the classpath.
I verified that the same thing happens with the test case in my environment. I didn't realize that one has to compile both *.java files to make it work. So now I need to work on getting a test case that demonstrates the problem: the problem still happens with the real code that I'm editing. One difference between the test case and the real code is that the real code is compiled, jared (jarred? jar'd?) and the *.jar file is in $CLASSPATH. But the *.class files are NOT in $CLASSPATH. Another difference is that the real project has a prj.el file whereas the test case didn't have one. I'm sure that this is pilot error; I just don't know what I'm doing wrong. Kai
