AbstractMethodError expected rather than IncompatibleClassChangeError for invocation on abstract method on iface

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: P3
    • hs25
    • Affects Version/s: None
    • Component/s: hotspot

      Given the following (indirectly compiled in such a way to avoid errors):

      interface J { int m(); }
      interface I extends J { default int m() { return J.super.m(); } }
      class C implements I {}

      C c = new C(); c.m(); // expected: AME; actual: ICCE

      An AbstractMethodError is expected but due to recent changes in Hotspot for the support of private methods this has changed to an IncompatibleClassChangeError.

            Assignee:
            Karen Kinnear (Inactive)
            Reporter:
            Paul Sandoz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: