v2.6.1

What's Changed

Bug Fixes

• Update Year in License by @Chrimle in #341

  Updates the year in all license files to 2024-2025.

Full Changelog: v2.6.0...v2.6.1

v2.6.0

What's Changed

New Features

• Include LICENSE.txt in the mustache-templates Artifact by @Chrimle in #335

  Adds a LICENSE.txt file to the mustache-templates artifact. This file will be included in the imported .jar file, in the root directory.

Dependency Updates

• Bump org.apache.maven.plugins:maven-deploy-plugin from 3.1.2 to 3.1.3 by @dependabot in #325
• Bump org.apache.maven.plugins:maven-dependency-plugin from 3.6.0 to 3.8.1 by @dependabot in #326
• Bump com.fasterxml.jackson.core:jackson-annotations from 2.18.1 to 2.18.2 by @dependabot in #238
• Bump org.hibernate.validator:hibernate-validator from 8.0.1.Final to 8.0.2.Final by @dependabot in #268
• Replace com.google.code.findbugs:jsr305 with com.github.spotbugs:spotbugs-annotations by @Chrimle in #332
• Bump com.github.spotbugs:spotbugs-annotations from 3.1.12 to 4.8.6 by @dependabot in #333

Full Changelog: v2.5.3...v2.6.0

v2.5.3

What's Changed

Bug Fixes

• Remove Transitive Dependencies from mustache-templates Artifact by @Chrimle in #317

  Removes all transitive dependencies from the mustache-templates artifact. These dependencies, used only for testing, have been relocated to the tests module. Importing the mustache templates should not require any dependencies; this has now been fixed. In the event of issues, please refer to the tests module for the relevant dependencies and their versions.

Full Changelog: v2.5.2...v2.5.3

v2.5.2

What's Changed

Bug Fixes

• Public Release of the parent Maven Artifact by @Chrimle in #312

  Releases the parent Maven Artifact for the first time. This artifact is required for the mustache-templates artifact, as it is it´s parent project. This solves the issue introduced in v2.5.1, which led to not being able to import the mustache-templates artifact.

Full Changelog: v2.5.1...v2.5.2

v2.5.1

What's Changed

Bug Fixes

• Add Ending Dot to Placeholder values in JavaDocs by @Chrimle in #282

  Adds a dot . to the end of placeholder values in JavaDocs. This is to improve readability and consistency. This only affects placeholder values, and will not append a dot to the end of any user-provided values.

Full Changelog: v2.5.0...v2.5.1

v2.5.0

What's Changed

New Features

• Reformat & Rephrase Generated JavaDocs by @Chrimle in #274

  Enhances all JavaDocs in generated record and enum classes by correcting grammatical issues and adhering more to the Google-Java-Format. This affects the placeholder JavaDocs in generated classes, but does not change any behavior or functionality.

Dependency Updates

• Bump org.apache.maven.plugins:maven-resources-plugin from 3.2.0 to 3.3.1 by @dependabot in #267
• Bump junit-jupiter.version from 5.11.3 to 5.11.4 by @dependabot in #272

Full Changelog: v2.4.0...v2.5.0

v2.4.0

What's Changed

New Features

• Support OpenAPI x-field-extra-annotation property by @Chrimle in #245

  Added support for the OpenAPI property x-field-extra-annotation. This property is optional, and will annotate the generated field with the provided annotations. NOTE: there is a formatting issue inherited from openapi-generator-maven-plugin which does not correctly indent the annotations. This change is fully backwards-compatible.

Full Changelog: v2.3.0...v2.4.0

v2.3.0

What's Changed

New Features

• Support OpenAPI x-class-extra-annotation property by @Chrimle in #209

  Adds support for the OpenAPI property x-class-extra-annotation (vendor-extension). The property can be set either as a string (for one annotation), or as a literal block |- (for multiple annotations). The property is only applicable for record classes. The property could conflict with additionalModelTypeAnnotations when referring to the same annotation (if the annotation is not repeatable).

Full Changelog: v2.2.1...v2.3.0

v2.2.1

What's Changed

Bug Fixes

• Support non-String values in fromValue() methods of generated enum classes by @Chrimle in #235

  Fixed 2 bugs related to the fromValue()-method in generated enum classes. The first, affected all generated enum classes where the type-property was not set to string. The fromValue()-method would always generate the method parameter as String, leading to issues caused by comparing incompatible types. The second issue is encountered under the same conditions, but when the configOption useEnumCaseInsensitive is set to true. This would invoke equalsIgnoreCase on non-String objects - which caused compilation errors. Both of these bug fixes are contained to the fromValue()-method and are fully backwards-compatible.

Full Changelog: v2.2.0...v2.2.1

v2.2.0

What's Changed

New Features

• Add Bean Validation @Email annotation to fields with format: email by @Chrimle in #224

  Added Bean Validation for String fields with the format property set to email. This property value will annotate the generated field with @Email. Requires the useBeanValidation configOption to be set to true. The format property remains optional.

Full Changelog: v2.1.1...v2.2.0