Bug 100970

Summary:	[1.5][compiler] Interface methods may conflict with Object methods
Product:	[Eclipse Project] JDT	Reporter:	Philipe Mulet <philippe_mulet>
Component:	Core	Assignee:	Kent Johnson <kent_johnson>
Status:	VERIFIED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	mlists
Version:	3.1
Target Milestone:	3.1.2
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Philipe Mulet

2005-06-20 17:50:37 EDT

Build 3.1rc3

The following program should compile ok:

interface I {
	void clone();
}

In 1.4 mode, it must complain as it does; but in 1.5 mode it must tolerate this
situation.

Also see bug 94759 for closely related issue in same area.

Comment 1 Philipe Mulet

2005-06-20 17:54:57 EDT

Slight modification of the previous code yields an error against J which doesn't
make much sense to me, as J doesn't implement the interface, it simply extends it.

interface I {
	@Override void clone();
}

interface J extends I {
}

Comment 2 Philipe Mulet

2005-09-23 06:18:44 EDT

Fix will not be ready for 3.1.1, removing target milestone "3.1.1"

Comment 3 Kent Johnson

2005-10-18 18:24:22 EDT

Added MethodVerify test074

Released into HEAD and 3.1.2 stream

Comment 4 Philipe Mulet

2006-01-10 07:14:11 EST

Better testcase:
interface I {
	void clone();
}
interface J extends I {
}

should only yield a warning on I (cannot be implemented), but no error on J.
Also compliance doesn't seem to be involved. We should always behave consistently throughout compliance modes.

Comment 5 Frederic Fusier

2006-01-10 07:18:26 EST

Verified in 3.1.2 using build M20060109-1200.

Comment 6 Frederic Fusier

2006-01-10 09:08:46 EST

Verified for 3.2 M4 using build I20051215-1506.