Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 30759 - Tag Local Copy of Files with a Version
Summary: Tag Local Copy of Files with a Version
Status: RESOLVED DUPLICATE of bug 36958
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 2.1   Edit
Hardware: All All
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 64961 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-01-31 18:43 EST by Brian Schultheiss CLA
Modified: 2005-05-09 14:37 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Schultheiss CLA 2003-01-31 18:43:11 EST
It would be nice if there were a feature that would allow you to tag the local 
copy (history) of your files in the Workspace with a version. This is very 
similar to tagging a version in CVS.

The difference is that there are many times when you would like to take a 
snapshot of your current workspace so that you can easily roll back to it.  
Examples of this are:
 1. You've got changes in your workspace, but you don't want to commit them to 
the CVS repository...however you need to take the latest copy from the server 
into your environment. In this scenario, someone trashed some code that causes 
your uncommitted changes to no longer work. In this case, it would be nice to 
be able to roll your entire workspace back to what it looked like prior to the 
update from CVS.
  2. You are working on some code that is in an invalid state so you don't want 
to commit it to CVS, however you are about to manually or automatically perform 
a refactoring that is going to have some far reaching changes.  You get done 
with those changes and you'd really like to get back to your previous 
state...no go though.

Basically, if you've ever used Visual Age for Java, your local Workspace had 
it's own versioning system...that's basically what I am suggesting.
Comment 1 Kevin McGuire CLA 2003-02-07 16:43:50 EST
It would be cool, and I think there's a bug report already for this.  But its 
hard -- we don't have a local history store that supports this.
Comment 2 Jean-Michel Lemieux CLA 2004-06-01 10:44:14 EDT
*** Bug 64961 has been marked as a duplicate of this bug. ***
Comment 3 Michael Valenta CLA 2005-05-09 14:33:20 EDT
Moving to Resources since they provide the local history.
Comment 4 John Arthorne CLA 2005-05-09 14:37:26 EDT

*** This bug has been marked as a duplicate of 36958 ***