Bug 3439 - Classfile comparator should be able to ignore synthetics (1GL2I3N)
Summary: Classfile comparator should be able to ignore synthetics (1GL2I3N)
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: All Windows NT
: P3 normal (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Olivier Thomann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:55 EDT by Philipe Mulet CLA
Modified: 2002-01-11 09:08 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 Philipe Mulet CLA 2001-10-10 22:55:08 EDT 
In order to minimize incremental builder actions, the classfile comparator should be able to ignore synthetics.
Note that this should be optional and not cost on cases where nothing has changed.
The intent is that this mechanism can be turned on/off so as for the builder to experiment.

NOTES:

OT (05/10/2001 1:32:07 PM)
	A different number of fields or methods means that something changed. So if a synthetic field disappeared, I think we can conclude that a change occured and recompile the
	class.
Comment 1 Olivier Thomann CLA 2001-10-18 12:15:08 EDT 
Done and tests added for 206.
Released in HEAD as soon as 205 is built.
Comment 2 DJ Houghton CLA 2001-10-29 17:14:11 EST 
PRODUCT VERSION:
SDK 202a