| Compile oddity [message #170218] |
Sun, 14 December 2003 17:11 |
Eclipse User |
|
|
|
I've been fighting some odd problems with compiles since installing
2.1.2. I looked through the bugzilla list for issues that have been
fixed in 2.1.2 but didn't see anything that sounded like what I'm seeing.
One of the problems manifested itself as compile errors that stated
some class names could not be found in my class file. These classes were
all in the same package so no imports are needed. Yet if I select one of
these classes and invoke the 'open definition' action, the class is
found and opened in a new editor. I got around this by building the
plug-in into a jar file (without touching the code) and then adding the
jar file to the project classpath. It immeadiately compiled. Then I went
back removed this jar file and it continues to compile fine. Seems it
gets into a wacky state and I can't get it out of it (this has happend
twice in the last two days).
The second problem I've seen is similar but I don't have an exact
scenario to give. Again they are compile errors that don't make sense
(i.e. there really shouldn't be an error flagged). The work around I
found for these other problems is to select all contents of the file,
delete, repaste and save. Bingo, the compile errors go away. Very
strange. This process doesn't work for the first problem I described.
I downloaded 2.1.2 and reinstalled. This did not fix the problem. Any ideas?
Mark
|
|
|
Powered by
FUDForum. Page generated in 0.03637 seconds
Home