Bug ID: JDK-6399361 CONFORMANCE: @Override specification and compiler inconsistent

Versions (Unresolved/Resolved/Fixed)

The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.

JDK 6
6 b86Fixed

FULL PRODUCT VERSION :


A DESCRIPTION OF THE PROBLEM :
@Override indicates that a method declaration is intended to not only override but also implement a method declaration in a superclass.
http://java.sun.com/docs/books/jls/third_edition/html/names.html#6.4.3
-----
abstract class C1 {
    public void m1() {
    }

    public abstract void m2();
}

class C2 extends C1 {
    @Override
    public void m1() {
    }

    @Override
    public void m2() {
    }
}
-----
Please revise the documentation (http://download.java.net/jdk6/docs/api/java/lang/Override.html) or the implementation.
The JLS should explain it more strictly, too.
http://java.sun.com/docs/books/jls/third_edition/html/interfaces.html#9.6.1.4


REPRODUCIBILITY :
This bug can be reproduced always.

EVALUATION See http://blogs.sun.com/ahe?entry=override for an informal discussion of alternative solutions.
11-05-2006
EVALUATION Actually, the compiler is correct and the specification is correct. The method C2.m2 overrides the method C1.m2 (and implements it). See JLS3 8.4.8.1, Overriding (by Instance Method). However, the specification is very convoluted and confusing. There are other examples which the compiler does not get right: public interface Test { void m(); } abstract class A implements Test { // m() is inherited from Test } class B extends A { @Override public void m() {} } Since m is a member of A, class B is overriding a method from a superclass. The compiler rejects this program. The best solution to this problem is to change both the compiler and the specification of @Override: * Indicates that a method declaration is intended to override a * method declaration in a supertype. If a method is annotated with * this annotation type but is not in fact override-equivalent to any * method declared in a supertype, compilers are required to generate * an error message.
10-05-2006
EVALUATION Perhaps the documentation of Override is wrong. The JLS is unclear in this area and should be clarified.
23-04-2006
EVALUATION The compiler appears to be wrong. However, fixing this might cause compatibility problems so we should consider if the compiler should be fixed or if the JLS should be changed.
16-03-2006

Duplicate :	JDK-6326485 - Compiler does not enforce rule that interfaces may not use @Override
Relates :	JDK-6409362 - A non-abstract method does not override an abstract one
Relates :	JDK-6424261 - Description of "override" in JLS 3 section 6.4.3 is misleading.
Relates :	JDK-6709448 - CONFORMANCE:@Override specification and compiler inconsistent 2
Relates :	JDK-6501053 - Specification of java.lang.Override was not updated when integrating 6399361
Relates :	JDK-6954234 - JDK 1.6 @Override: Implementation different from Specification
Relates :	JDK-5008260 - @Override should be generalized from 'superclass' to 'supertype'