Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313998 - CVS "file modified" decorators not cleared after committing a patch
Summary: CVS "file modified" decorators not cleared after committing a patch
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-21 20:15 EDT by Martin Oberhuber CLA
Modified: 2022-02-26 11:04 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 Martin Oberhuber CLA 2010-05-21 20:15:49 EDT
Build ID: I20100520-1744 on WinXP SP3

This was a one-time occurrence only, I didn't have time to try reproduce. Here is what I did:

1. Synchronize workspace.
2. Apply a patch in JDT perspective / package explorer (modified 3 Java files).
   History view was not visible at that time.
3. Team > Synchronize to review the patch. Do slight modifications in the
   Team Synchronization perspective.
4. Run > Debug to test the patch.
5. Back in JDT perspective, pick the package which contains the 3 modified 
   files. See 3 files (and package, and project) with CVS ">" indicators
   for "modified".
6. Right-click > Create patch. Save as a file.
7. Right-click > Commit.

--> At this point, the ">" indicators are normally cleared. For me, though, they remained.

8. Pick project, Team > Synchronize. See dialog "No changes in project".
--> The ">" indicators are still there. The "local version" displayed in 
    package explorer is still the base version.

9. Pick one of the modified files. Right-click > Team > History.
--> At this point, the ">" indicators were gone, and base version was updated.

10. Open the Error Log View. No exceptions of any kind seen.
Comment 1 Tomasz Zarna CLA 2010-05-24 05:48:07 EDT
I gave it a try using I20100523-0800, but didn't succeed ie I wasn't able to reproduce it with the given steps. Martin, please let us know if this happens again and you have more reliable steps.
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:33:03 EDT
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.
Comment 3 Eclipse Genie CLA 2022-02-26 11:04:10 EST
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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.