Re: [gmf-dev] compiler error blocking build

[Christian Damus <cdamus@xxxxxxxxxx>]

Hi,

I have committed a fix (with Linda's
help), renaming the offending method to getMSLCrossReferenceAdapter().

Actually, this should not have been
a compile error; looks like a bug in the JDT compiler.  Static methods
cannot conflict in this way with different return types because they are
not polymorphic.  The compiler generates invokeSpecial bytecodes that
bind statically to the type and method, so there is never an issue of conflict.

Oh, well.

Christian

---

Christian W. Damus
Aurora Core Model Services
IBM Rational Software
Tel: (613) 591-7937
-- If at first you do succeed, try to hide
your astonishment.

"Richard Gronback" <Richard.Gronback@xxxxxxxxxxx>
Sent by: gmf-dev-bounces@xxxxxxxxxxx

02/03/2006 09:07 PM

Please respond to
"GMF Project developer discussions."

To	"GMF Project developer discussions." <gmf-dev@xxxxxxxxxxx>, "GMF Release List" <gmf-releng@xxxxxxxxxxx>
cc
Subject	[gmf-dev] compiler error blocking build

Hi All,
 
I’ve entered this bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=126443
 
It seems the latest integration build settings
we should now all be targeting produces a compiler error.  Apparently,
EMF added a method of the same name/arg but with a different return type
on a class we extend.
 
The current config is listed here: http://download.eclipse.org/technology/gmf/downloads/drops/I-I20060203-200602030830/index.php
 
Thanks,
Rich
 
Richard C. Gronback
Borland Software Corporation
richard.gronback@xxxxxxxxxxx
+1 860 227 9215
 _______________________________________________
gmf-dev mailing list
gmf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gmf-dev