Description Heiko Sommer 2004-01-22 06:24:17 EST

When developer A imports a new Eclipse project into CVS using the command line 
("cvs import -m ..."), the files appear in CVS with revision number "1.1.1.1".
Let's assume that developer B subsequently checks out this project using 
Eclipse.

Quoting from http://cvsbook.red-bean.com/cvsbook.html: "It concerns a special 
meaning that CVS attaches to revision 1.1.1.1. For most purposes, we can just 
say that files receive a revision number of 1.1 when imported, but the number 
is displayed — for reasons known only to CVS — as 1.1.1.1 in the Entries file, 
until the first commit."

Strange as this may seem, the cvs command line deals with it correctly, which 
means always interpreting "1.1.1.1" as "HEAD:1.1".

Eclipse gets it right when developer A commits a change to a 1.1.1.1-file: this 
file then appears as revision 1.2 in CVS.

However, when developer B does a "Synchronize with Repository..." in Eclipse, 
he won't see the change that A has made. Eclipse behaves in this situation as 
if B had checked out a branch 1.1.1.1, and therefore won't see changes on HEAD.
In order for B to get the changes, he must do a "Replace With - Latest From 
HEAD", which is a poor workaround, given that there should be no branches at 
this state of the project.

I think that Eclipse should recognize the weird magic meaning of "1.1.1.1" in 
CVS.
Note that this problem does not occur when the project was initially checked 
into CVS with Eclipse; Eclipse seems to use "cvs add" instead of "cvs import", 
which assigns initial revision numbers "1.1" to each file.