[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.tools] M5 error with finding Java classes and ability to import automatically

A wonderful feature in M3 does not appear to
work in M5. Can anyone point me to how I
can change my configuration to make this
work again?

In 2.1 M3 (on Windows 2000 with a 1.4.0 JDK),
I can type in the name of a class that I
haven't imported yet. Eclipse flags this as
an error (correctly) and notes that the
type, say Foo, cannot be resolved or is not
a type. Click on the lightbulb icon and
Eclipse will helpfully offer to import
the class. Other handy choices
(generally not what I want) are to create
a new class of that name, create an
interface of that name, or change to
a similar name (in the case of a mis-typed
name).

With M5, I cannot figure out how to get Eclipse
to offer to import my class. That is, Eclipse
no longer seems to know about this class. This is
for the same codebase where this feature works
in M3.

Some quirks of my environment, which I am
hoping will lead someone to point me to
a preference to change, are:

1. I'm using the Perforce Team Provider.
(http://sourceforge.net/projects/p4eclipse/)
This has worked from 2.02 onwards. It seems
to work fine in M5.

2. My project was created by the Perforce
perspective (select a directory and "Check Out
as Project"). This means it isn't a "Java Project",
so I have manually created a .classpath file.

3. My sources are stored under a subdirectory
of a directory named src. For example,
src/layer1
src/layer2
src/layer3

For three different layers of a system. The
.classpath file names all these directories
as a classpathentry of kind=src and
the path is correct. In the M3 release, this
was enough to allow Eclipse to find my classes
and perform the really really nice automatic
import.

4. The problem occurs whether I swith the Java/New Project
preferences source and output folder to Project
or Folders (src and bin) or not.

5. The problem also continues to occur even if
I add the source directory in question to the
classpath as a Java/Classpath Variable.

So, what do I need to do to get this to
work again in the M5 release?

Any help would be appreciated.

Thanks,
-Eric