Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 357483 - Files remain marked as changed after commit
Summary: Files remain marked as changed after commit
Status: CLOSED DUPLICATE of bug 329555
Alias: None
Product: Subversive
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Igor Burilo CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-13 09:02 EDT by Iger CLA
Modified: 2011-09-26 12:39 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Iger CLA 2011-09-13 09:02:18 EDT
Build Identifier: 20110615-0604

Hello!

Quite often, after I commit a tree of changed files into SVN, some of the files still stay marked as uncommitted. In history view I see them marked as previous revision (as if the switch to the freshly created revision didn't happen) but if I compare such a file with repository I can see, that the last version is there - and there are no changes. In SVN Info the files is marked as Text Status: Modified.

The effect went away a couple of times after svn cleanup, but usually, I either need to "Override and Update" or, for to Reopen the project with the file.

The problem occurs at 2 different rather fresh Eclipse Indigo installations, I don't remember encountering this bug on the Helios builds...

I also don't see anything interesting in SVN console...

Reproducible: Sometimes

Steps to Reproduce:
1. Modify/Create a few files
2. Try to Commit them (either through Team Synchronize or through Navigator)
3. Observe some files still marked as changed in Navigator and/or left in the Team Synchronize view
Comment 1 Iger CLA 2011-09-13 09:05:28 EDT
Just to clarify, when I wrote "the effect went away" I didn't mean that it stopped happening, just that the specific files that were marked as changed became unmarked for this specific commit. On the next commit - some other files messed up.
Comment 2 Alexander Gurov CLA 2011-09-26 12:39:33 EDT
Looks like duplicate for the bug #329555.

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