Description alincoln 2004-07-29 13:11:33 EDT

Eclipse 3.0 routinly loses references to import declarations on individual 
classes.  This occurs whenever the project/source code is zipped up and moved 
to a different PC...i.e. when code is exchanged during development.  A typical 
class may have the following import declarations at the top:

<snip>
import java.io.IOException;

import com.synapsegroupinc.rwframework.iface.IDataVO;
import com.synapsegroupinc.rwframework.iface.IWriter;
</snip>

When that class and/or project gets moved to a different computer, and the 
project gets re-opened in Eclipse, one or more of those import's appears as an 
error... "... can not be resolved...".  The work-around is currently to re-
type part(s) or all of the import declaration.  In some cases, it's much 
worse, you need to actually go to the class being referenced ( IDataVO, 
IWriter ) and make an editing change, then the class can be found.

This also occurs even though the project gets moved to a directory 
tree/structure that mirrors the original directory tree/structure.

Current Profile
------------------------------------------------
Windows XP Professional
Eclipse 3.0
CDT Plugin 2.0.0
EclipseColorer 0.6.0
JDK 1.3.1-03 ( For project compilations )
JDK -vm 1.4.1-07 ( Only to run Eclipse 3.0 )

The problem also appears to occur on referenced projects as well as external 
JARs.  I have not seen it lose import declarations on any Java/JDK imports.

thx,

alincoln@edgewater.com