Bug 44331 - Need indication that removal/add was targeted to a primary working copy
Summary: Need indication that removal/add was targeted to a primary working copy
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M4   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-07 12:48 EDT by Dirk Baeumer CLA
Modified: 2003-10-14 10:54 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 Dirk Baeumer CLA 2003-10-07 12:48:31 EDT 
I20031007

In the case were a primary working copy gets discarded with no underlying 
resource the Java model delta reports a remove with details == 0. The details 
should be set to primary working copy to distinguish this from a "normal" 
remove. Corresponding a add should do the same.
Comment 1 Jerome Lanneluc CLA 2003-10-07 13:15:34 EDT 
Added F_PRIMARY_WORKING_COPY flag on primary working copy addition 
(becomeWorkingCopy()) and on primary working copy deletion (discardWorkingCopy
()) when there is no corresponding resource.

Changed WorkingCopyOwnerTests.testDeltaBecomeWorkingCopy2() and 
testDeltaDiscardPrimaryWorkingCopy3() to reflect this change.
Comment 2 David Audel CLA 2003-10-14 10:54:29 EDT 
Verified.