Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 369300

Summary:	many comparator "unexpected" messages when moving to new (M4) JDT compiler
Product:	[WebTools] WTP Releng	Reporter:	David Williams <david_williams>
Component:	releng	Assignee:	Carl Anderson <ccc>
Status:	ASSIGNED ---	QA Contact:	Carl Anderson <ccc>
Severity:	normal
Priority:	P3	CC:	tranle1
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description David Williams

2012-01-20 17:05:55 EST

http://build.eclipse.org/webtools/committers/wtp4x-R3.4.0-I/20120120182304/I-3.4.0-20120120182304/testResults.php

There are about 80 "unexpected" comparator messages where .class files changed with respect to the reference repository. 

From past experience, these are all likely non-significant changes, such as the JDT compiler doing a better job of leaving out dead code, or similar, but, should at least "spot check" a few of them, but suspect the "fix" is just to retag effected bundles, to make sure the newly compiled versions have a different qualifier and are the ones we end up distributing.

Comment 1 Tran Le

2012-01-25 12:39:35 EST

I have re-tagged the Dali bundles.

Comment 2 Carl Anderson

2012-01-25 12:44:37 EST

I worry that, with the upcoming JDT changes in M5, we will have more unexpected messages in these same bundles... and perhaps, some of the changes that cause the comparator messages will be fixed/reverted.  I think we should deal with this later in M6, once we are using M5 to build, and that these comparator messages should not be considered blocking for M5.