Description Magda Bologa 2007-01-17 15:12:08 EST

There is a Refresh issue in CVS Repository View when Commit a file to CVS Repository (the old version from Head will show up e.g. v.1.1 in CVS Repository View instead of the new committed file e.g. v. 1.2 – this can be confusing for user because if he perform a Compare With ->HEAD from CVS Repositories View, will report differences if you did not refresh CVS Repository View after committing your files
If the user will Perform Refresh View Command from Context menu in CVS Repositories View in RSx, when Compare With ->HEAD from CVS Repositories View will report  no differences anymore (version will increase in CVS Repository for your file from 1.1. to 1.2 and no differences reported

Steps:
User1:
In the Java Perspective:
- Create a Java Project with a Java Class Class1.java and add to CVS Source Control (from Team->Share Project context menu in Java Perspective) 
- Commit all to CVS repository

User2:
- As different user check-out the Java Project from CVS Repository Exploring - - Check the revision version of Class1.java file - should be version 1.1 (for example)
- In the Java Perspective, modify Class1.java as user2 save and Commit to CVS Repository
-Switch to CVS Repository Exploring  Perspective 
Actual: notice that the version of Class1.java is still 1.1 instead of 1.2 - 
You need to perform Refresh View to get the latest version from HEAD

- If user does not refresh the CVS Repository EXploring View and perform a Compare with ->Head from context menu of the revision in CVS Repositories View, differences will be reported from version 1.1 to version 1.2 (even if the version in head is 1.2 and the local version is 1.2 as well (since user2 commited changes)

- If user does Refresh the CVS Repository Exploring View, Class1.java will show as version 1.2 and when perform a Compare with ->Head from context menu of the revision in CVS Repositories View, no differences will be reported