Community
Participate
Working Groups
HEAD. Create a 1.5 project with the following classes: public class Character implements Comparable<Character> { public int compareTo(Character obj) { return 0; } } public interface Comparable<T> { public int compareTo(T obj); } Create a 1.4 project that depends on the 1.5 project with the following: public class X { Object fValue; public int compareTo(Object obj) { return ((Character)fValue).compareTo(obj); } } See that during reconcile we report an error: The method compareTo(Character) in the type Character is not applicable for the arguments (Object) while the code compiles OK. (as it should). Basically the call gets bound to the bridge method if Character & Comparable were to be binary types, but we don't seem to handle this case where we materialize the source type from the model.
See also bug 330347
The model gets populated just after parse and is unaware of synthetics.
(In reply to comment #2) > The model gets populated just after parse and is unaware of > synthetics. So looks like we need to arrange to have method verification done on the Source Type materialized from the model.
Don't expect to get to it in time for M4. Will revisit later.
Created attachment 228698 [details] Another test case Here's even a more tricky case: the compliance of the affected project is 1.6 but the JRE is 1.4 on it. Test Case: 1. import the two projects 2. open 'A' ==> reconciler reports error Using a 1.6 EE fixes the problem.
(In reply to comment #5) > Created attachment 228698 [details] > Another test case > > Here's even a more tricky case: the compliance of the affected project is > 1.6 but the JRE is 1.4 on it. > > Test Case: > 1. import the two projects > 2. open 'A' > ==> reconciler reports error > > Using a 1.6 EE fixes the problem. I can't reproduce the error with these steps. Is it still reproducible for you on 4.3 RC4?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
