Community
Participate
Working Groups
Build Identifier: I20110613-1736 Although the option General | Compare/Patch | Ignore white space is checked, if you compare a local file with its remote revision and the only differences are the line ending characters, the Synchronize View shows the local file as modified Reproducible: Always Steps to Reproduce: 1. checkout a file from CVS 2. change its line ending character (for instance, from CR to CRLF); do not do any other change and save 3. in Package/Project Explorer the file is marked as modified: this is ok 4. do a Team => Synchronize with Repository on the containing folder 5. the Synchronize View is populated: I would expect the file to be reset to "up-to-date", so that it is not shown in the Synchronize View and the ">" is removed from the Package/Project Explorer too, since there are no real differences with its latest remote revision; in fact, if I double click on it in the Synchronize View to see the differences, I do not see any one! 6. however, the file is still marked as modified; if I try to commit, CVS does not actually commit, because I think the CVS client doesn't find any real difference to commit 7. the result is that, even if I have committed, the file is still shown as modified (with outgoing changes), both in the Synchronize View and in the Package/Project Explorer; there is no way to fix this problem other than doing an "Override and Update" from the CVS repository; if you try just an "Update", the CVS says there are no differences to merge I'm pretty sure that with older versions of Eclipse this problem didn't occur: as soon as you did a "Synchronize with repository", if the file was not really modified in its contents, its state was reverted to "up-to-date". I may be wrong, but with the latest versions of Eclipse (even 3.6.x I think, but I can't remember well) I find myself in this odd situation rather often...
This could be related to bug 315747. I'm planning to have a closer look what's going on there. Please stay tuned.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.