AutoValue 1.6.3

• Make AutoValue and AutoService support Gradle incremental build. Thanks to Thomas Broyer for this work. (a5673d0)
• When hashCode() is @Memoized, equals() will be optimized to check hash codes first before other properies (34a6a03)
• MemoizeExtension recognises @Nullable type annotations, not just method annotations. (66a57ec)
• Remove unnecessary parentheses from the generated equals(Object) method in @AutoValue classes. (a5387a6)
• Clarify the AutoValueExtension documentation to explain how subclassing works in the code generated by extensions. (73e848a)
• GwtSerialization support now works in the presence of AutoValue extensions. (9cc04ec)
• Remove the need for the java.desktop module on Java 9+. (f878642)

Auto Factory 1.0-beta6

• Do not prepend outer classnames to the generated @AutoFactory class name if a class name has been explicitly specified. (b79c170)
• Java 9 support
• Add support for type-annotations and CheckerFramework nullable types to @AutoFactory (4d6df14)

AutoValue 1.6.2

• Add capability to annotate individual AutoValue fields. (96370f3)
• Ensure AutoAnnotation works even if there is no @Generated available. (32a0ae3)
• Use separate EscapeVelocity project rather than AutoValue's own copy. (b5b51db)
• Delete AutoValue's copy of EscapeVelocity. (a36cc06)

AutoValue 1.6.1

• Reformatted AutoValue source code using google-java-format. (41d78d2)
• 9057ae8:
  Allow an Optional property to be set in a builder through a method with a @Nullable parameter.
  NOTE: As a side-effect of this change, a setter for a @Nullable property must have its parameter also marked @Nullable. Previously, if the @Nullable was not a TYPE_USE @Nullable, it was copied from the getter to the parameter of the generated setter implementation. For TYPE_USE @Nullable it was already necessary to mark the setter parameter @Nullable.

---

• Clarified how annotation copying works when @CopyAnnotations is not present. (0808746)
• In @AutoValue class Foo<@Bar T>, copy @Bar to the implementing subclass. (c830cf2)
• If an @AutoOneOf class has @CopyAnnotations, copy class annotations to the generated subclasses. (521cc94)

Auto Value 1.6

• @AutoValue, @AutoAnnotation, @AutoOneOf, and @Memoized are now in a separate artifact, auto-value-annotations. This allows users to specify the annotations in compile scope and the processor in an annotation processing scope, without leaking the processor to a release binary. To upgrade to this version of auto-value, you'll need to add this new artifact as a dependency. (0c488d7)

(note, this is equivalent to auto-value-1.6rc1)

Auto Value 1.6 - rc1

• @AutoValue, @AutoAnnotation, @AutoOneOf, and @Memoized are now in a separate artifact, auto-value-annotations. This allows users to specify the annotations in compile scope and the processor in an annotation processing scope, without leaking the processor to a release binary. To upgrade to this version of auto-value, you'll need to add this new artifact as a dependency. (0c488d7)

AutoValue release 1.5.4

• Copy type annotations from the parameter of equals(Object) to its implementation. (1561e2c)

• Don't include AutoValue's sources in its Maven jar. (d61a969)

• Ensure that @AutoValue classes have correct code even if redeclarations of Object or String are in scope. (6a41d3a)

• Add support for new @AutoOneOf. (6ee8d68)

AutoCommon release 0.10

• Add an implementation of generatedAnnotation that uses the source version instead of classpath introspection. (0383c1c)
• Add SimpleAnnotationMirror and SimpleTypeAnnotationValue to easily create new AnnotationMirrors in code. (6d9cc58)

AutoValue release 1.5.3

• Use @javax.annotation.processing.Generated for Java 9. (f04406c)
• Rework the logic for imports in AutoValue. (39b9987)
• Change retention of @AutoValue.Builder and @AutoValue.CopyAnnotations to CLASS rather than SOURCE. (d528f7f)
• Fix bug where java.util.Arrays was sometimes imported but not used. (ed1d3fe)

AutoService release 1.0-rc4

• Allow @autoservice to accept multiple service providers (c02f839)