David,
I can confirm that this is a 3.7 compiler issue related somehow to the extending/implementing of interfaces. The same code compiles fine in my 3.6 development
environment and duplicates the compile errors in the 3.7 environment I just set up. Unfortunately, trying to understand how the EMF interfaces/classes are pieced together has revealed how little I understand EMF at the moment. The problem classes appear
to be EMF generated, so with my very limited knowledge of EMF, I would not be able to supply a timely fix, other than to switch back to the 3.6 compiler.
Larry
From: wtp-releng-bounces@xxxxxxxxxxx [mailto:wtp-releng-bounces@xxxxxxxxxxx]
On Behalf Of David M Williams
Sent: Wednesday, December 15, 2010 4:45 AM
To: wtp-releng@xxxxxxxxxxx
Subject: [wtp-releng] Compile errors in org.eclipse.jst.server.generic.core?
In the latest 3.3 build, there were a number of "illegal cast" compile errors in org.eclipse.jst.server.generic.core.
Was this due to a change in org.eclipse.jst.server.generic.core?
I ask because I am fairly sure all the pre-reqs were exactly the same as previous build (where there were no compile errors) but I did change the version of our "base builder" which (mostly) means previously builds were compiled with a 3.6 based JDT compiler,
but now are compiled with a 3.7 M4 based compiler. Could there have been a change there to cause this? Or a change in defaults ... former warnings now caught as errors?
Even though we do not have a "declared build" this week, I'd appreciate understanding this issue quickly (EOD Wednesday?), to know if we have a problem with our M4 deliverables ... or, if someone just casually checked in some code with errors?
Thanks,
