| Eclipse automatically creates build path errors [message #162772] |
Fri, 04 June 2004 10:10 |
Eclipse User |
|
|
|
Originally posted by: matuszek.central.cis.upenn.edu
In Eclipse 3.0RC1 I had a mysterious error with one of my projects. It had
the error flag next to the
project name and the package name, but nowhere in the source code. The
Build command did
nothing. The Run command told me the class file was missing (correctly,
because the Build did
nothing). I got NO information about what was wrong.
The error turned out to be that I had gotten a couple of other (closed)
projects listed as required
in the build path. When I deleted these from the build path, I was able
to compile and run.
If the other projects HAD been required, I would have gotten a "cannot be
resolved (or is not a valid
type)" message at each point I tried to use those projects. Since the
projects were there by accident, I
got errors but no error messages of any kind, and I had to stumble my way
to a solution.
I have since discovered how the projects got added to my build path. They
were added automatically
when I opened the project, because these other projects were already open.
Apparently this "feature" was added by someone who only works on one
project at a time. Okay, I can
work around this by being sure to close each project before I open the
next one, but I'd rather have
the ability to move freely among projects (as before). Does anyone know
how to turn this "feature" off?
Many thanks!
Dave Matuszek
|
|
|
Powered by
FUDForum. Page generated in 0.05234 seconds
Home