java.lang.IncompatibleClassChangeError when using Java-class, which implements @interface

[scabug]

When invoking method from instances of class, which implement interfaces, declared in Java as public @interface SomeInterface - then throws java.lang.IncompatibleClassChangeError. But if use that in Java classes - all works fine. Now to solve this problem used workaround which use static methods from Java-class with additional argument of this-object.
for example:

// In Java
public @interface TableColumn {
	int width() default -1;
}
public class TableColumnImpl implements TableColumn {.......}
public class TableWorkAround { 
 public int width(TableColumnImpl column) { return column.width();}
}

// In Scala
...
val column: TableColumnImpl = getSomeFuncReturn_TableColumnImpl
val widthScala = column.width // throw IncompatibleClassChangeError
val widthJava = TableWorkAround.width(column) // works fine

when disassembly
in scala call of method -> invokeinterface
in java call of method -> invokevirtual

Full bundle, which replicates this behaviour in bundle.zip, which attached

[scabug]

Imported From: https://issues.scala-lang.org/browse/SI-8348?orig=1
Reporter: Sergey Zaytsev (serghy)
Affected Versions: 2.10.2, 2.10.3, 2.11.0-M8
Attachments:

• bundle.zip (created on Feb 27, 2014 6:53:26 AM UTC, 1521 bytes)

[scabug]

@soc said (edited on Feb 27, 2014 2:03:56 PM UTC):
Not sure what you are trying to do, but TableColumn is not an interface, it's an annotation.
It's probably a bug, but why are you subclassing annotations in the first place?

[scabug]

Sergey Zaytsev (serghy) said:
We use this for mixing "static logic" of anotation to "dynamic logic" on runtime. In Java, it did not cause problems, and we did not expect them to appear in Scala. Use the workaround is not convenient, especially when a lot of methods. And abandon Scala is also not desirable.

[hrhino]

This appears to have been fixed as a by-product of scala/scala@7d51b3f.