Community
Participate
Working Groups
When the compiler creates the missing abstract method (problem method), it should also tag them as synthetic methods. Without this, any tooling (including API tooling) cannot make a difference between an actual method defined in the class and the one added because it is missing. See bug 224685 in API tooling land where a wrong delta (ADDED method) is reported when the method is not defined in the source.
Created attachment 94047 [details] Proposed fix
I can take care of this one. Philippe, let me know if you believe this makes sense.
Pls go ahead.
All tests passed successfully with this patch. Kent, do you see anything wrong with this patch? It is more about secondary errors that I am worried about.
Released for 3.4M7.
Added regression test org.eclipse.jdt.core.tests.builder.ErrorsTests#test0106
Created attachment 94589 [details] Proposed fix New fix that sets the AccSynthetic bit directly when the method binding is created for the missing abstract problem methods. This needs to be applied after the first patch as it removes the first change in the ClassFile class.
Verified for 3.4M7 using I20080429-0100