Home » Newcomers » Newcomers » Issue with CVS update
| Issue with CVS update [message #257339] |
Wed, 28 May 2008 11:42  |
Eclipse User |
|
|
|
Originally posted by: ourrubbish.gmail.com
Hello,
I am unable to properly synchronize my local sandbox against my CVS
repository. I am able connect to the server and commit my own changes to
files I already have locally. But when a teammate commits a new file,
the synchronization dialog (Team->Syncronize) does not show such file. I
have also tried to Team->Update with the same results. I would expect
any new files to show up in the resolution dialog as incoming additions.
I have been able to work around this by opening the view "CVS Repository
Exploring", manually browse until I find the files which were added by
the other developer (after being informed of their existence and
location), choosing "Check Out As..." from the context menu, and
selecting the intended destination in my local sandbox.
Needless to say, the workaround is far from ideal. I suppose I am
missing a fundamental notion here. Why do new files show up in
Repository Exploring but seem to be missed by the Update/Synchronize
operations? I have searched extensively online for answers to this issue
to no avail.
Thanks in advance to any kind souls out there,
--R
|
|
| | | |
| Re: Issue with CVS update [message #258301 is a reply to message #258279] |
Thu, 12 June 2008 12:07  |
| Eclipse User |
|
|
|
Originally posted by: ourrubbish.gmail.com
R.A. wrote:
> Eric Rizzo wrote:
>> R.A. wrote:
>>> Hello,
>>>
>>> I am unable to properly synchronize my local sandbox against my CVS
>>> repository. I am able connect to the server and commit my own changes
>>> to files I already have locally. But when a teammate commits a new
>>> file, the synchronization dialog (Team->Syncronize) does not show
>>> such file. I have also tried to Team->Update with the same results. I
>>> would expect any new files to show up in the resolution dialog as
>>> incoming additions.
>>
>> The only thing I can think of is that one of you is actually on a
>> branch while the other is on HEAD. If you don't have any pending local
>> changes, try to right-click the project and choose Replace with... >
>> Another branch of version... and then select HEAD. If you do that at
>> the project level (not any subdirectory), you'll be sure to be pointed
>> at HEAD.
>>
>> Hope this helps,
>> Eric
>
> I have verified that this happens while we are both on HEAD. It also
> seems like it only occurs with folders, i.e. when someone creates a
> subfolder under a folder that was previously committed and visible from
> all clients (in all the local copies). I would much appreciate any
> insight into this.
>
> Thanks,
>
> R.A.
I have figured out that the problem is due to the absence of the '-d'
switch on cvs update, which instructs CVS to create new directories. The
question now is how do I get Eclipse to issue a -d switch when I perform
a Team Update.
Thanks again,
R.A.
|
|
|
| Re: Issue with CVS update [message #258314 is a reply to message #258301] |
Thu, 12 June 2008 15:22 |
| Eclipse User |
|
|
|
Originally posted by: codeslave.ca.ibm.com
Make sure every folder on the server has at least one file in it -- even
a hidden .dotfile -- and Eclipse will create the folder in your
workspace. I've used .placeholder, .cvsignore, .htaccess, .classpath...
depends on your use case, of course.
R.A. wrote:
> R.A. wrote:
>> Eric Rizzo wrote:
>>> R.A. wrote:
>>>> Hello,
>>>>
>>>> I am unable to properly synchronize my local sandbox against my CVS
>>>> repository. I am able connect to the server and commit my own
>>>> changes to files I already have locally. But when a teammate commits
>>>> a new file, the synchronization dialog (Team->Syncronize) does not
>>>> show such file. I have also tried to Team->Update with the same
>>>> results. I would expect any new files to show up in the resolution
>>>> dialog as incoming additions.
>>>
>>> The only thing I can think of is that one of you is actually on a
>>> branch while the other is on HEAD. If you don't have any pending
>>> local changes, try to right-click the project and choose Replace
>>> with... > Another branch of version... and then select HEAD. If you
>>> do that at the project level (not any subdirectory), you'll be sure
>>> to be pointed at HEAD.
>>>
>>> Hope this helps,
>>> Eric
>>
>> I have verified that this happens while we are both on HEAD. It also
>> seems like it only occurs with folders, i.e. when someone creates a
>> subfolder under a folder that was previously committed and visible
>> from all clients (in all the local copies). I would much appreciate
>> any insight into this.
>>
>> Thanks,
>>
>> R.A.
>
> I have figured out that the problem is due to the absence of the '-d'
> switch on cvs update, which instructs CVS to create new directories. The
> question now is how do I get Eclipse to issue a -d switch when I perform
> a Team Update.
>
> Thanks again,
>
> R.A.
--
Nick Boldt :: Release Engineer, IBM Toronto Lab
Eclipse Modeling :: http://www.eclipse.org/modeling
http://wiki.eclipse.org/index.php/User:Nickb
|
|
|
| Re: Issue with CVS update [message #258317 is a reply to message #258314] |
Thu, 12 June 2008 15:44 |
| Eclipse User |
|
|
|
Originally posted by: ourrubbish.gmail.com
I'm afraid this is already the case. The folder I'm trying to update
does contain several committed files on the server. It seems to me like
Eclipse is failing to issue a -d option to actually request new folders
to be created.
> Nick Boldt wrote:
> Make sure every folder on the server has at least one file in it -- even
> a hidden .dotfile -- and Eclipse will create the folder in your
> workspace. I've used .placeholder, .cvsignore, .htaccess, .classpath...
> depends on your use case, of course.
>
> R.A. wrote:
>> R.A. wrote:
>>> Eric Rizzo wrote:
>>>> R.A. wrote:
>>>>> Hello,
>>>>>
>>>>> I am unable to properly synchronize my local sandbox against my CVS
>>>>> repository. I am able connect to the server and commit my own
>>>>> changes to files I already have locally. But when a teammate
>>>>> commits a new file, the synchronization dialog (Team->Syncronize)
>>>>> does not show such file. I have also tried to Team->Update with the
>>>>> same results. I would expect any new files to show up in the
>>>>> resolution dialog as incoming additions.
>>>>
>>>> The only thing I can think of is that one of you is actually on a
>>>> branch while the other is on HEAD. If you don't have any pending
>>>> local changes, try to right-click the project and choose Replace
>>>> with... > Another branch of version... and then select HEAD. If you
>>>> do that at the project level (not any subdirectory), you'll be sure
>>>> to be pointed at HEAD.
>>>>
>>>> Hope this helps,
>>>> Eric
>>>
>>> I have verified that this happens while we are both on HEAD. It also
>>> seems like it only occurs with folders, i.e. when someone creates a
>>> subfolder under a folder that was previously committed and visible
>>> from all clients (in all the local copies). I would much appreciate
>>> any insight into this.
>>>
>>> Thanks,
>>>
>>> R.A.
>>
>> I have figured out that the problem is due to the absence of the '-d'
>> switch on cvs update, which instructs CVS to create new directories.
>> The question now is how do I get Eclipse to issue a -d switch when I
>> perform a Team Update.
>>
>> Thanks again,
>>
>> R.A.
>
|
|
| |
| Re: Issue with CVS update [message #258350 is a reply to message #258317] |
Thu, 12 June 2008 16:49 |
| Eclipse User |
|
|
|
Originally posted by: codeslave.ca.ibm.com
Try replacing a parent folder from cvs, or else check the whole project
out again into a new project name.
Sometimes Eclipse gets confused when dealing with children that have
changed, but a refresh from the top-down can often fix that.
R.A. wrote:
> I'm afraid this is already the case. The folder I'm trying to update
> does contain several committed files on the server. It seems to me like
> Eclipse is failing to issue a -d option to actually request new folders
> to be created.
>
> > Nick Boldt wrote:
>> Make sure every folder on the server has at least one file in it --
>> even a hidden .dotfile -- and Eclipse will create the folder in your
>> workspace. I've used .placeholder, .cvsignore, .htaccess,
>> .classpath... depends on your use case, of course.
>>
>> R.A. wrote:
>>> R.A. wrote:
>>>> Eric Rizzo wrote:
>>>>> R.A. wrote:
>>>>>> Hello,
>>>>>>
>>>>>> I am unable to properly synchronize my local sandbox against my
>>>>>> CVS repository. I am able connect to the server and commit my own
>>>>>> changes to files I already have locally. But when a teammate
>>>>>> commits a new file, the synchronization dialog (Team->Syncronize)
>>>>>> does not show such file. I have also tried to Team->Update with
>>>>>> the same results. I would expect any new files to show up in the
>>>>>> resolution dialog as incoming additions.
>>>>>
>>>>> The only thing I can think of is that one of you is actually on a
>>>>> branch while the other is on HEAD. If you don't have any pending
>>>>> local changes, try to right-click the project and choose Replace
>>>>> with... > Another branch of version... and then select HEAD. If you
>>>>> do that at the project level (not any subdirectory), you'll be sure
>>>>> to be pointed at HEAD.
>>>>>
>>>>> Hope this helps,
>>>>> Eric
>>>>
>>>> I have verified that this happens while we are both on HEAD. It also
>>>> seems like it only occurs with folders, i.e. when someone creates a
>>>> subfolder under a folder that was previously committed and visible
>>>> from all clients (in all the local copies). I would much appreciate
>>>> any insight into this.
>>>>
>>>> Thanks,
>>>>
>>>> R.A.
>>>
>>> I have figured out that the problem is due to the absence of the '-d'
>>> switch on cvs update, which instructs CVS to create new directories.
>>> The question now is how do I get Eclipse to issue a -d switch when I
>>> perform a Team Update.
>>>
>>> Thanks again,
>>>
>>> R.A.
>>
--
Nick Boldt :: Release Engineer, IBM Toronto Lab
Eclipse Modeling :: http://www.eclipse.org/modeling
http://wiki.eclipse.org/index.php/User:Nickb
|
|
|
Goto Forum:
Current Time: Sun Jun 22 13:38:12 EDT 2025
Powered by FUDForum. Page generated in 0.09445 seconds |
Home