Community
Participate
Working Groups
Build ID: M20070921-1145 Steps To Reproduce: 1. User modifies some files. 2. After synchronizing, there are files to be updated (commited by another user) and files to be commited (modified on step 1) 3. User commits the whole project 4. User updates the whole project 5. Files modified in step 1 that were commited are now with the second last revision (before modifications). If the user synchronizes again, these files appear as to be updated, commited by our main user (himself). After updating the whole project, files are in the last revision state. 6 Note: If user opts to update the project before committing, no problem arises. More information: We have about 20 developers, all of them using MyEclipse 6.0.1 (Eclipse 3.3.1 with lastest Subversion and SVNKit 1.x versions). SVN server is the lastest 1.4.x version.
The problem is happened because Synchronize View restricts update by revisions which are received from server in time of synchronization in order to update only changes which are approved by user. Unfortunately committed files' revisions are greater than revisions stored in Synchronize View, so the files committed are updated back to the revisions stored in Synchronize View. The only one possible solution for this problem is to perform updates to HEAD revision Synchronize View stored resources. The bad side of this fix is that you do not know exactly what you get after performing an update from a Synchronize View. Fix will be available in the weekly build.
*** Bug 241941 has been marked as a duplicate of this bug. ***
*** Bug 241572 has been marked as a duplicate of this bug. ***
