#9013 CVS Commit problem

When I select and commit changed files to CVS from a change list, they get committed into CVS, but the local workspace copies are not updated with the CVS changes (revision numbers, keyword expansions, etc.), so they remain on the change list.

When I re-committed these files, thinking I'd forgotten to do so, the CVS archive versions were updated (another revision number, another set of keywork expansions) but the local workspace copies remained unchanged, and still on the changes list...

This is a nasty problem, as you now have to manually update the files (or the project) after committing them before they correctly match the CVS archive versions.

Edited by: Dave Lorde on Nov 14, 2008 12:45 PM

2 comments
Comment actions Permalink

Please check whether manual synchronization (CtrlAltY) would help.

Is it a repeatable problem?

Can we get a more specific description maybe?

Edited by: Irina Chernushina (JetBrains) on Nov 14, 2008 5:59 PM

0
Comment actions Permalink

Please check whether manual synchronization (CtrlAltY) would help.

Manual IDEA caches synchronization (CtrlAltY) did help - when it had finished, the committed files were gone from the change list. But it's not an acceptable solution, as 1. It's manual and 2. It takes several minutes.

Is it a repeatable problem?

Yes. It happens every time I commit.

Can we get a more specific description maybe?

More specific in what way? I commit files, but they remain in the change list and don't get updated to match the new CVS revisions until a manual update or cache synchronization is done.

0

Please sign in to leave a comment.