Bug 18436 - deleting multiple fields triggers multiple builds (if editor closed) [ccp]
Summary: deleting multiple fields triggers multiple builds (if editor closed) [ccp]
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.1 RC1   Edit
Assignee: Adam Kiezun CLA
QA Contact:
URL:
Whiteboard:
Keywords: investigate
Depends on:
Blocks:
 
Reported: 2002-05-31 09:30 EDT by Adam Kiezun CLA
Modified: 2003-02-19 14:01 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 Adam Kiezun CLA 2002-05-31 09:30:30 EDT 
we delete fields by calling 'delete' in a loop
(unlike other members which we delete all in one go by using text edits)

this results in:
. multiple builds when you have the editor closed
. multiple local history entries

(not sure how to fix though)
Comment 1 Erich Gamma CLA 2002-05-31 12:59:21 EDT 
can you do it inside a workbench runnable?
Comment 2 Erich Gamma CLA 2002-06-05 02:19:04 EDT 
defer
Comment 3 Dirk Baeumer CLA 2002-07-22 06:34:16 EDT 
The workbench runnable might reduce the numbers of builds to one. Deleting a 
field is done via JDOM (AFAIK) which save the file.

So why don't we use the same code as we use to delete methods ?
Comment 4 Dirk Baeumer CLA 2003-01-20 11:46:52 EST 
Adam, can you test if this still exists. If so we should ask Java Core how to 
avoid this.
Comment 5 Adam Kiezun CLA 2003-02-19 14:01:05 EST 
it was fixed today