Bugzilla – Full Text Bug Listing
| Summary: | [compiler] Inconsistent name clash behavior vis-a-vis javac7 | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Satyam Kandula <satyam.kandula> |
| Component: | Core | Assignee: | Srikanth Sankaran <srikanth_sankaran> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | srikanth_sankaran, stephan.herrmann |
| Version: | 3.7 | ||
| Target Milestone: | 3.8 M5 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
I will take a look at this. This problem no longer occurs in BETA_JAVA8 branch. Resolving as WORKSFORME. 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 *** |
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); }