Bug 3315 - (minor) Class wizard creates three copies in history (1GFMJLS) [code manipulation]
Summary: (minor) Class wizard creates three copies in history (1GFMJLS) [code manipula...
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All Windows NT
: P3 normal (vote)
Target Milestone: 2.1 M5   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:53 EDT by John Arthorne CLA
Modified: 2003-02-05 02:44 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 John Arthorne CLA 2001-10-10 22:53:05 EDT 
The "New Class" wizard seems to be inefficient.  If you create a simple class with no superclass
or interfaces, or methods, and hit finish, the local history will contain three identical copies of the class.
It doesn't make sense that it should have to create three copies of the file.

NOTES:
EG (6/20/2001 6:08:29 AM)
	known problem, can't be changed now.

MA (31.07.2001 17:32:06)
	These are from manipulations done using Java Core routines (creating the body, adding the imports, adding methods,
	adding more imports, formatting).
	Even everything is done in one IWorkspaceRunnable, multiple local history entries are created.
	Java Core needs to honor IWorkspaceRunnable or provide something similar.
	Move to JCore

MA (28.08.2001 19:51:19)
	see also 1GEUGFQ: ITPJUI:ALL - Adding new class takes very long (>20s)
Comment 1 DJ Houghton CLA 2001-10-29 17:08:54 EST 
PRODUCT VERSION:

0.125
Comment 2 Philipe Mulet CLA 2002-06-13 12:36:03 EDT 
Need some JavaModelRunnable operation support.
Deferring
Comment 3 Philipe Mulet CLA 2002-09-20 05:54:48 EDT 
Duplicate of 3248
Comment 4 Philipe Mulet CLA 2002-09-20 05:59:14 EDT 
Closing as duplicate

*** This bug has been marked as a duplicate of 3248 ***
Comment 5 Philipe Mulet CLA 2002-09-23 04:31:35 EDT 
It appears to be a UI defect (should use working copies). If using compilation 
units, then our behavior is fine.

Moving to JDT/UI for disposal (still a dup of bug 3248).
Comment 6 Dirk Baeumer CLA 2003-02-05 02:44:30 EST 
We are now using working copies for this as suggested by Philippe. Works fine for 
integration build I20030129.