Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 116474 - Synchronize view update action doesn't update an addition
Summary: Synchronize view update action doesn't update an addition
Status: RESOLVED DUPLICATE of bug 101633
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-15 13:31 EST by Ryan Manwiller CLA
Modified: 2005-11-15 14:37 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Manwiller CLA 2005-11-15 13:31:58 EST
This is on the 3.2 M3 build.

There is a java file addition showing in my synchonize view. I choose "update"
or "update all incoming changes". I can see in the console the cvs command being
run and having an 'ok' status, but the workspace does not contain the new file.
And the file remains as an incoming addition in the synchronize view.

Can't repro consistently. Other additions seemed to update just fine.

***
cvs update -l -d -P "/myproject/src/com/ibm/example/Hello.java"
ok (took 0:00.125)
***
Comment 1 Ryan Manwiller CLA 2005-11-15 13:32:47 EST
There were no errors in the error log.
Comment 2 Michael Valenta CLA 2005-11-15 14:04:34 EST
We've seen this with transient additions (i.e. added before the sync, deleted 
before the update). Was the file in question deleted from the repo before you 
had a chance to update?
Comment 3 Ryan Manwiller CLA 2005-11-15 14:25:39 EST
I think this was a transient addition. So it makes sense that the update doesn't
do anything. However, I synchronized again, and the addition is still showing in
the sync view. I would expect it to realize the file has been removed and clear
it from the sync view.
Comment 4 Michael Valenta CLA 2005-11-15 14:37:04 EST
Yes, I agree. I was just confirming it was the same case.

*** This bug has been marked as a duplicate of 101633 ***