Bug 348377 - [compiler] Inconsistent name clash behavior vis-a-vis javac7
Summary: [compiler] Inconsistent name clash behavior vis-a-vis javac7
Status: CLOSED DUPLICATE of bug 354229
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.8 M5   Edit
Assignee: Srikanth Sankaran CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-06 05:59 EDT by Satyam Kandula CLA
Modified: 2013-03-10 14:41 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Satyam Kandula CLA 2011-06-06 05:59:48 EDT 
The following program triggers a name clash error from javac 7 while eclipse compiles it silently.
abstract class Y implements A<String>, B<Integer> {
	public abstract boolean foo(Number other);                       
}                                                                       
interface A<T> { boolean foo(T other); }                   
interface B<T> { boolean foo(T other); }
Comment 1 Satyam Kandula CLA 2011-06-06 06:00:26 EDT 
I will take a look at this.
Comment 2 Srikanth Sankaran CLA 2013-03-10 05:44:24 EDT 
This problem no longer occurs in BETA_JAVA8 branch. Resolving as WORKSFORME.
Comment 3 Stephan Herrmann CLA 2013-03-10 14:41:47 EDT 
Seeing that this has been fixed between 3.8M4 and 3.8M5 I'm taking a
guess at what bug might have fixed this issue.

*** This bug has been marked as a duplicate of bug 354229 ***