Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 315937

Summary: Revision information not shown
Product: [Technology] Subversive Reporter: olly2 Mising name <o.huckfeldt>
Component: UIAssignee: Igor Burilo <igor.burilo>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: 0.7   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description olly2 Mising name CLA 2010-06-07 04:38:01 EDT
Build Identifier: 20090619-0625

Using Subversive it is not possible to show the revision information of files and folders in your local working copy. In the preferences you can enable text decorations including a "revision" information, which is active by default, but this does not show the revision but the last changed revision ("last revision loaded into workspace").

Let me say that the last changed revision is a powerful and necessary information and I do not want to miss it. But from time to time I definitly need the pure revision information as shown by svn status -v or svnversion.

Reproducible: Always

Steps to Reproduce:
1. Start Eclipse, open a project that is connected to a svn server
2. Update to the latest revision
3. Now you still see a mixed revisions
Comment 1 olly2 Mising name CLA 2010-06-17 01:51:15 EDT
First I want to make this assumption: lets say you make an update of your WC, so there are no incoming changes. After that you change some files and commit them. Like this you end up with a situation with no incoming changes but a mixed revision WC.

I personally see two use cases when it is very helpful to check your WC whether it is a single or mixed revision WC.


1.: Merging.
It is recommended and as far as I can see best practise to have a single revision WC before merging.

2.: Branching based on local WC.
When creating a branch based on local WC you shopuld also have a single revision WC (strongly recommended). I know that it is not absolutly necessary to create the branch based on WC - but in the real world not everybody is a SVN expert. In our company a lot of people do a lot of things, and just one of that is working with SVN. Creating a branch based on the WC seems to be more intuitive then creating a server site branch.
Comment 2 Igor Burilo CLA 2010-06-21 05:16:39 EDT
I agree with you that working copy should be in single revision for merge and branching, although it's SVN recommendation, and to follow this recommendation you can call Update action, so Subversive provides enough functionality to make a single revision WC. From the other side knowing whether we have a mixed revision WC could be sometimes useful, but if we find that this functionality highly usable and desirable by users we'll add it in the future.
Thanks for your notes. 

Close as WONTFIX.