Kai Grossjohann writes: > Paul Kinnucan <[EMAIL PROTECTED]> writes: > > > Kai Grossjohann writes: > > > Then position point after "this." and invoke jde-complete (in one of > > > its flavors). Observe how it adds an import statement for > > > javax.swing.Action. > > > > This is because javax.swing.Action is the only class on the classpath > > at this point. Compile your Action class and then retry the completion. > > The JDEE should then prompt you to choose one of the Action classes > > to import. > > Hm. I just invoked "javac Action.java", then tried again. Now I get > "no completion". The environment variable $CLASSPATH starts with > ".:", and Action.class is in the current working directory, together > with Action.java and BTest.java.
What is the setting of jde-resolve-relative-paths-p? Paul > > But this was just a test case, in the real code that I've got, I see > the same behavior I described originally, even though the code has > been compiled many times on this machine already, and a corresponding > *.jar file is mentioned in $CLASSPATH. > > Originally, I thought that the problem comes from the "import foo.*" > statements in the *.java file -- I normally don't use asterisks in > import statements but the author of the file in question doesn't want > me to expand them. Then I made this test case and observed the same > error. > > What can I do to track down the problem? Something weird must be > going on, but I don't know where to start looking. > > Kai >
