v1.5.0

Enables more powerful generated ADTs via #38 and #39, courtesy of @andyglow.

v1.4.1

Use javax.annotation:javax.annotation-api instead of javax.annotation:jsr250-api for JSR250 annotations via #32 .

v1.4.0

Adds support for copying over annotations from specifications to generated code, via #31. New minor version since the presence of annotations in generated code may lead to different bytecode (and may thus introduce build issues, though probably only if something is incorrectly set up), but should not lead to ABI incompatibilities.

v1.3.3

Improve Javadocs in generated code, via #30.

v1.3.2

Fixes #28, regarding using arrays leading to SpotBugs violations in generated code.

v1.3.1

Fixed a bug that prevented referring to sets of dataenums in a dataenum_case via #21

v1.3.0

Changes included:

• Makes this an incremental annotation processor when used with Gradle via #17.
• Ensure generated code doesn't violate SpotBugs with fb-contrib via #18.
• Permit any annotation named "Redacted" when redacting toString output via #19.

v1.2.0

Adds the ability to redact field values in toString methods via #16.

v1.1.0

Contains two changes:

• #12, which improves the error messages for duplicated case names (introduced via method overrides in the @DataEnum specification interface).
• #14, which changes the access level of generated constructors by default and makes it configurable.

v1.0.2

This release contains two main changes:

• It removes support for varargs case parameters (#4) . This is actually an API-breaking change, but we decided to ignore that, as it is very unlikely that anyone would run into problems from that in practice. The rationale for removing is that varargs/arrays are quite problematic from a safety perspective.
• It fixes an issue where the generated code for DataEnums with type parameters caused the compiler to issue warnings (#6).