| Problem with classpath after closing Eclipse 3.0RC2 [message #254350] |
Mon, 21 June 2004 18:16  |
Eclipse User |
|
|
|
Originally posted by: mar.almaden.ibm.com
I've just moved up to using Eclipse 3.0RC2 and have noticed a problem
which looks like a project's classpath is getting corrupted either on
exit or startup of Eclipse.
Starting with a new workspace, I can checkout 4 plugin projects we've
been developing from our cvs. The workbench does a full build of the
4 projects and there are no compilation errors. If I then exit Eclipse
and restart Eclipse, the projects rebuild and have numerous compile
errors. Alternately, if I checkout the projects allow the workbench
to compile the projects (showing no errors) and then perform a
Project->Clean (Clean All Projects) then the recompiled projects end up
with numerous errors.
These projects do not have compile errors as it compiles immeadiately
after checking out from the cvs and can be run without any problems. It
is only after eclipse rebuilds the project that compile errors turn up.
To eliminate the possibility of a harddisk problem I have tested this on
two different machines both running Windows XP. The problem existed on
both machines.
Any suggestions on what may be happening and how to resolve this would
be appreciated.
Thanks,
Michael Richmond
|
|
|
| Re: Problem with classpath after closing Eclipse 3.0RC2 [message #254414 is a reply to message #254350] |
Mon, 21 June 2004 22:28  |
| Eclipse User |
|
|
|
Originally posted by: mar.almaden.ibm.com
Michael Richmond wrote:
> I've just moved up to using Eclipse 3.0RC2 and have noticed a problem
> which looks like a project's classpath is getting corrupted either on
> exit or startup of Eclipse.
>
> Starting with a new workspace, I can checkout 4 plugin projects we've
> been developing from our cvs. The workbench does a full build of the
> 4 projects and there are no compilation errors. If I then exit Eclipse
> and restart Eclipse, the projects rebuild and have numerous compile
> errors. Alternately, if I checkout the projects allow the workbench
> to compile the projects (showing no errors) and then perform a
> Project->Clean (Clean All Projects) then the recompiled projects end up
> with numerous errors.
>
> These projects do not have compile errors as it compiles immeadiately
> after checking out from the cvs and can be run without any problems. It
> is only after eclipse rebuilds the project that compile errors turn up.
> To eliminate the possibility of a harddisk problem I have tested this on
> two different machines both running Windows XP. The problem existed on
> both machines.
Update: It turns out that one of these projects did not include
org.eclipse.core.resources or org.eclipse.ui.ide in the plugin.xml file
for the project. After adding these entries the project compiles fine on
subsequent attempts.
What this means is that for the automatic compile after checking out
from the cvs repository then eclipse must be including at least
org.eclipse.core.resources in the build path automatically. On
subsequent builds eclipse is only using the entries in the classpath.
My theory is that the .classpath file from the cvs is being used during
the automatic build immeadiately after checkout and then sometime during
the build the classpath is being re-computed based on the contents of
the plugin.xml file in the project. This theory would explain the
behaviour I have been seeing. However, it seems that both the automatic
build and any subsequent builds should both use the same .classpath.
Opened bug 68127 for this problem.
|
|
|
Powered by
FUDForum. Page generated in 0.03060 seconds
] 
Search
Help
Register
Login
Home
