Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369300 - many comparator "unexpected" messages when moving to new (M4) JDT compiler
Summary: many comparator "unexpected" messages when moving to new (M4) JDT compiler
Status: ASSIGNED
Alias: None
Product: WTP Releng
Classification: WebTools
Component: releng (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Carl Anderson CLA
QA Contact: Carl Anderson CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-20 17:05 EST by David Williams CLA
Modified: 2012-01-25 12:44 EST (History)
1 user (show)

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 David Williams CLA 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 CLA 2012-01-25 12:39:35 EST 
I have re-tagged the Dali bundles.
Comment 2 Carl Anderson CLA 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.