What causes java.lang.IncompatibleClassChangeError?

最新推荐文章于 2024-09-04 10:58:10 发布

WangMark

最新推荐文章于 2024-09-04 10:58:10 发布

阅读量273

点赞数

分类专栏： Android开发

Android开发专栏收录该内容

114 篇文章

订阅专栏

本文详细解析了 Java 中 IncompatibleClassChangeError 的原因，包括类库不向后二进制兼容导致的问题，例如非最终字段变为静态、类变成接口等。还列举了可能引发的其他异常，并推荐了一些检测此类变化的工具。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

https://stackoverflow.com/questions/1980452/what-causes-java-lang-incompatibleclasschangeerror

80 down vote

Your newly packaged library is not backward binary compatible (BC) with old version. For this reason some of the library clients that are not recompiled may throw the exception.

This is a complete list of changes in Java library API that may cause clients built with an old version of the library to throw java.lang.IncompatibleClassChangeError if they run on a new one (i.e. breaking BC):

Non-final field become static,
Non-constant field become non-static,
Class become interface,
Interface become class,
if you add a new field to class/interface (or add new super-class/super-interface) then a static field from a super-interface of a client class C may hide an added field (with the same name) inherited from the super-class of C (very rare case).

Note: There are many other exceptions caused by other incompatible changes: NoSuchFieldError, NoSuchMethodError, IllegalAccessError, InstantiationError, VerifyError, NoClassDefFoundError and AbstractMethodError.

The better paper about BC is "Evolving Java-based APIs 2: Achieving API Binary Compatibility" written by Jim des Rivières.

There are also some automatic tools to detect such changes:

Usage of japi-compliance-checker for your library:

japi-compliance-checker OLD.jar NEW.jar

Usage of clirr tool:

java -jar clirr-core-0.6-uber.jar -o OLD.jar -n NEW.jar

Good luck!