[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[platform-vcm-dev] Synchronize doesn't work with CVS for NT ?
|
I tried to find anything about it in bugs and mailing list archives but probably
I just missed it, so here is my question.
I will appreciate if somebody give me some link to workaround or solution if
it's described somewhere.
For some reason "Synchronize" doesn't work sometimes (I use F3, but noticed this
problems about a month ago).
It happens when somebody else updated resource and you have to synchronize or
when you have project which is not synchronized with module in CVS. If you
updated it by yourself (and have only outgoing changes) everything works fine.
Possible steps to generate such situation are:
1) Create project, i.e. "TestCVS"
2) Share project ("TestCVS" module created, ".project" committed)
3) Disconnect project (with "remove local CVS meta-info" or something like this
option)
4) Share project (when you try to do this it says that such module already
exists in CVS and asks if we want to synchronize it, and we are OK with
synchronize)
After it I shows either "Error fetching file revisions" if we had several
resources in our project before first sharing, or just "An error has occurred
processing file 'C:/CVSROOT/eclipse/TestCVS/.project 1.1'" in described test
case.
!SESSION Jun 14, 2002 18:14:06.74 ----------------------------------------------
java.version=1.4.0
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -Xmx256m -install
file:C:/Program Files/Eclipse/
!ENTRY org.eclipse.team.cvs.core 2 -21 Jun 14, 2002 18:14:06.74
!MESSAGE Host 'cvs' is running CVS NT (version 1.11.1.3) which is not fully
supported. However, most functionality is available.
!ENTRY org.eclipse.team.cvs.core 4 -6 Jun 14, 2002 18:14:16.619
!MESSAGE An error has occurred processing file
'C:/CVSROOT/eclipse/TestCVS/.project 1.1'
In some previous versions I saw stack trace with some words about invalid number
format when it tried to parse revision number or something, I just can't
reproduce it right now.
Thanks,
Alexander
