Bug 3233 - JM - CreateElementInCuOperation should not save working copy (1GBEKAW)
Summary: JM - CreateElementInCuOperation should not save working copy (1GBEKAW)
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: All Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 M4   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:51 EDT by Jerome Lanneluc CLA
Modified: 2002-03-12 06:32 EST (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 Jerome Lanneluc CLA 2001-10-10 22:51:43 EDT 
When using CreateElementInCUOperation on a working copy, its content is saved each time
	an element is added.

NOTES:

JBL (3/30/2001 4:13:36 PM)
	Once this is fixed, the class creation wizard should work on a working copy when creating the new class,
	then save the result. This would avoid unecessary saves (up to 4 saves are done right now).

JBL (6/18/2001 2:20:20 PM)
	Still true in 125.
Comment 1 DJ Houghton CLA 2001-10-23 23:52:19 EDT 
PRODUCT VERSION:
	JT 037
Comment 2 Jerome Lanneluc CLA 2002-03-12 06:32:43 EST 
Saving a working copy doesn't change the original cu's resource. It is done 
only when the working copy is committed.
Closing.