Bug 8479 - Ensure we are capturing local history
Summary: Ensure we are capturing local history
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.0   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Jean-Michel Lemieux CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-01-25 11:37 EST by Kevin McGuire CLA
Modified: 2002-04-09 09:15 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin McGuire CLA 2002-01-25 11:37:33 EST 
We have several PRs from 1.0 where we were not properly capturing local 
history.  The CORE IResource operations for move/delete have an option for 
whether local history should be kept.  We need to ensure we are using this 
option in the appropriate times.

For example, "Replace With -> Base/Revision" should store the current resource 
into local history before replacing.

Ensuring we are good local history citizens is a P1 plan item for 2.0.
Comment 1 Kevin McGuire CLA 2002-01-25 11:49:04 EST 
Clarification,

In the case of storing to local history prior to replace with base, 
specifically the case is if the local resource was modified/unreleased.  

If the user is replacing a resource for which we have an exact matching 
revision in the repository, the user could always get the state back from the 
repository history.
Comment 2 Jean-Michel Lemieux CLA 2002-03-06 17:15:56 EST 
Fixed. We are calling IFile.setContents() with preserve history as true. Every 
CVS operation done within Eclipse works on IResources, we will benefit from any 
Eclipse history mechanism from now on. We are no longer bashing the file system 
then refreshing local.