Bug 329250

Summary:	Wrong compile errors because 1.4 project doesn't see constructors/methods from 1.5 project
Product:	[Eclipse Project] JDT	Reporter:	Markus Keller <markus.kell.r>
Component:	Core	Assignee:	Srikanth Sankaran <srikanth_sankaran>
Status:	VERIFIED WORKSFORME	QA Contact:
Severity:	major
Priority:	P3	CC:	amj87.iitr, daniel_megert, deepakazad, Olivier_Thomann
Version:	3.7
Target Milestone:	3.7 M4
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Markus Keller

2010-11-02 07:16:11 EDT

HEAD, was OK in 3.7M3

- load org.eclipse.search.tests from
:pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse

=> Wrong compile errors, e.g. in AnnotationManagerTest:
It calls new "TestSuite(AnnotationManagerTest.class)", but apparently, the constructor
    public TestSuite(final Class<? extends TestCase> theClass) {...}\
cannot be found any more.

Comment 1 Markus Keller

2010-11-02 07:24:28 EDT

A similar compile error occurs in org.eclipse.jdt.core.formatter.CodeFormatterApplication:
NLS#initializeMessages(String, Class<?>) cannot be resolved here:

		static {
			NLS.initializeMessages(BUNDLE_NAME, Messages.class);
		}

Comment 2 Markus Keller

2010-11-02 07:49:45 EDT

Caused the fix for bug 328689.

Comment 3 Markus Keller

2010-11-02 07:59:27 EDT

> Caused the fix for bug 328689.
I meant:
Caused *by* the fix for bug 328689.

Comment 4 Olivier Thomann

2010-11-02 09:04:04 EDT

Srikanth, don't we also need the check for java.lang.Class (similar to what was done org.eclipse.jdt.internal.compiler.lookup.Scope.computeCompatibleMethod(MethodBinding, TypeBinding[], InvocationSite) line 538-542) inside 
org.eclipse.jdt.internal.compiler.lookup.Scope.parameterCompatibilityLevel(MethodBinding, TypeBinding[]) ?

Comment 5 Srikanth Sankaran

2010-11-02 11:38:40 EDT

We are still testing, but it appears that the fix for
bug 186565 also appears to address this problem. Stay
tuned.

Comment 6 Srikanth Sankaran

2010-11-02 12:20:52 EDT

(In reply to comment #5)
> We are still testing, but it appears that the fix for
> bug 186565 also appears to address this problem. Stay
> tuned.

Olivier confirmed (Thanks!) that both the scenerii
reported in comment#0 and comment#1 are covered by
the fix for 186565.

I close the current bug as WORKSFORME (since it is not
exactly a duplicate of bug 186565)

Comment 7 Ayushman Jain

2010-12-07 05:34:31 EST

Verified for 3.7M4 using build I20101205-2000.