Pojomatic – Changes in Pojomatic

Fix GitHub issue #16, which prevented Pojomatic from running on Java versions earlier than 9.

Move to using ASM 7, so that classes with nested classes compiled under JDK 11 or later can still be processed. Fixes GitHub issue #14.

Pojomatic now relies on ASM directly, instead of the repacked org.kohsuke:asm5 library. In particular, this means it is now compatible with Java versions 7 through 11. Moreover, as newer Java releases come out, it should be possible to upgrade to a newer ASM version without a new release of pojomatic. Fixes GitHub issue #10.
Pojomatic has been modularized under the name org.pojomatic. It can of course continue to be used as a jar, as well as now using it as a module. GitHub issue #13.
Fix GitHub issue #11 - generated doEquals method only considers properties also selected for hashCode.

Pojomatic now requires Java version 7 or higher
Pojomators are now created by generating byte code. The generated code uses InvokeDynamic rather than ordinary reflection to access properties.
Because, as of Java 7, the order in which fields and methods are returned by the Reflection API has become somewhat arbitrary, ASM is used to visit the byte code used to define the class, and determine the order of properties from that.
PojoFormatter has been deprecated in favor of the new EnhancedPojoFormatter. Similarly, DefaultPojoFormatter has been deprecated in favor of the new DefaultEnhancedPojoFormatter.
PropertyFormatter has been deprecated in favor of the new EnhancedPropertyFormatter. Similarly, DefaultPropertyFormatter has been deprecated in favor of the new DefaultEnhancedPropertyFormatter.
New annotation, SkipArrayCheck, provides an optimization for fields of type Object which should never be treated as arrays.

Simplification of the Differences API. As part of this simplification, Pojomatic.diff now requires that both arguments be non-null.
Add new method, Pojomatic.areCompatibleForEquals.

Pojomatic.equals() now properly handles inheritance, including comparing instances of two separate child classes of a parent class (bug 2845939).
A Pojomator can now be created for an interface.
New annotations, OverridesEquals and SubclassCannotOverrideEquals SubclassCannotOverrideEquals help control how inheritance is handled.
Properties from the parent class now come before those of the child in equals calculations and in the toString() representation.
Pojomatic will no longer add a method property multiple times if it is overridden (even if the overridden method is explicitly annotated).
Pojomatic.diff no longer requires a non-null first argument.

A new method, Pojomatic.diff, will show top-level differences between two instances of a pojomated class.
The property name derived from a method such as getFoo() is now "foo" instead of "getFoo" in the default toString() representation.
Names of properties in the default toString() representation can be overridden via the name attribute on the Property annotation.
Static fields and methods are no longer picked up by @AutoProperty (bug 2739467)