Version 1.28.2 (2026-01-23)

New Features / Improvements

• #676: Improve interoperability of generated code with other classes also using Jackson
  New behavior can be activated be setting configuration parameter generateJsonSetterAnnotationOnBuilderOperations to true in your Maven Plugin Configuration for JEAF Generator

Fixed Bugs

• #674: Missing @Valid annotation on fields of generic types

Migration

General Notes

• Jackson 3 support
  This version contains experimental support for Jackson 3 which by default is required for Spring Boot 4. Even though not all Spring Boot 4 specific tests are already completed, with this version we want to give early adopters the change to test Jackson 3 / Spring Boot 4 migration on their side.
  
  JEAF Generator is capable to generate Jackson 2 and 3 code within the same module. In order to make the behavior configurable we introduced several new configuration parameters: jacksonVersions, jackson2Suffix, jackson2Subpackage, jackson3Suffix and jackson3Subpackage
  
  For further details please look here: https://www.jeaf-generator.io/developer-guide/maven-plugin-configuration/#common-configuration-parameters
  
  For better backward compatibility with existing implementations and tests we strongly recommend to apply the following configuration changes for Jackson 3

// For better JSON backward compatibility with Jackson 2 we preserve the property order as it ws in Jackson 2
JsonMapper.builder().disable(MapperFeature.SORT_PROPERTIES_ALPHABETICALLY);

// If not working with generic builder pattern then in addition this setting is needed.
JsonMapper.builder().enable(MapperFeature.ALLOW_FINAL_FIELDS_AS_MUTATORS);

Version 1.28.x or earlier

• No special actions for migration needed

Version 1.27.x or earlier

• Upgrade of JEAF Generator Meta Model (JMM)
  Due to implementation of #337 and #624 changes in JMM were necessary. Before switching to version 1.28.* please upgrade your UML models to JMM Version 2.8.0 (revision #271 or #71 in MagicDraw Teamwork Cloud)
  
  

• Required changes in UML model
  Due to #492 there are case where you have to do changes in the UML model before upgrading. In order to fix #492 JEAF Generator no longer generates a custom implementation class in case of abstract classes with derived properties. If you still need this class then you have to set tagged value hasCustomImplementation to truein the UML model. If not you need to delete the currently generated custom class from your src directory as it will cause compile errors otherwise after the migration.
  
  

• JEAF Generator Extension API v2
  JEAF Generator now also supports a new version 2 of its extension API. If you want to make use of it then you need to explicitly enable that by implementing JEAFGeneratorExtensionAPI.ext and return 2 as supported version.

Links

For further information please refer to our documentation:

• JEAF Generator Website
• UML Modeling Guide
• Developer Guide

Version 1.28.1 (2026-01-16)

New Features / Improvements

• ❗ Experimental: Jackson 3 support (#664)

Fixed Bugs

• none

Migration

General Notes

• Jackson 3 support
  This version contains experimental support for Jackson 3 which by default is required for Spring Boot 4. Even though not all Spring Boot 4 specific tests are already completed, with this version we want to give early adopters the change to test Jackson 3 / Spring Boot 4 migration on their side.
  
  JEAF Generator is capable to generate Jackson 2 and 3 code within the same module. In order to make the behavior configurable we introduced several new configuration parameters: jacksonVersions, jackson2Suffix, jackson2Subpackage, jackson3Suffix and jackson3Subpackage
  
  For further details please look here: https://www.jeaf-generator.io/developer-guide/maven-plugin-configuration/#common-configuration-parameters
  
  For better backward compatibility with existing implementations and tests we strongly recommend to apply the following configuration changes for Jackson 3

// For better JSON backward compatibility with Jackson 2 we preserve the property order as it ws in Jackson 2
JsonMapper.builder().disable(MapperFeature.SORT_PROPERTIES_ALPHABETICALLY);

// If not working with generic builder pattern then in addition this setting is needed.
JsonMapper.builder().enable(MapperFeature.ALLOW_FINAL_FIELDS_AS_MUTATORS);

Version 1.27.x or earlier

• Upgrade of JEAF Generator Meta Model (JMM)
  Due to implementation of #337 and #624 changes in JMM were necessary. Before switching to version 1.28.* please upgrade your UML models to JMM Version 2.8.0 (revision #271 or #71 in MagicDraw Teamwork Cloud)
  
  

• Required changes in UML model
  Due to #492 there are case where you have to do changes in the UML model before upgrading. In order to fix #492 JEAF Generator no longer generates a custom implementation class in case of abstract classes with derived properties. If you still need this class then you have to set tagged value hasCustomImplementation to truein the UML model. If not you need to delete the currently generated custom class from your src directory as it will cause compile errors otherwise after the migration.
  
  

• JEAF Generator Extension API v2
  JEAF Generator now also supports a new version 2 of its extension API. If you want to make use of it then you need to explicitly enable that by implementing JEAFGeneratorExtensionAPI.ext and return 2 as supported version.

Links

For further information please refer to our documentation:

• JEAF Generator Website
• UML Modeling Guide
• Developer Guide

Version 1.28.0 (2026-01-08)

New Features / Improvements

• Automatically use Java Wrapper types in REST controller instead of Java primitives in case of optional OpenAPIDataTypes (#34)
• SoftLinks for derived properties (#577)
• Support type wildcards for generics (#641)
• Add check for optional primitives without default value (#8)
• OpenAPI uniqueItems not supported (#320)
• Define per OpenAPIDataType if it should implement java.lang.Comparable (#337)
• Allow to explicitly add @Override annotation to Java code (#624)

Fixed Bugs

• Useless class generated in case of abstract class with derived property (#492)
• Report does not contain example values for properties (#635)
• Line breaks are not preserved in OpenAPI spec (at least SwaggerUI) (#645)

Migration

Version 1.27.x or earlier

• Upgrade of JEAF Generator Meta Model (JMM)
  Due to implementation of #337 and #624 changes in JMM were necessary. Before switching to version 1.28.0 please upgrade your UML models to JMM Version 2.8.0 (revision #271 or #71 in MagicDraw Teamwork Cloud)
  
  

• Required changes in UML model
  Due to #492 there are case where you have to do changes in the UML model before upgrading. In order to fix #492 JEAF Generator no longer generates a custom implementation class in case of abstract classes with derived properties. If you still need this class then you have to set tagged value hasCustomImplementation to truein the UML model. If not you need to delete the currently generated custom class from your src directory as it will cause compile errors otherwise after the migration.
  
  

• JEAF Generator Extension API v2
  JEAF Generator now also supports a new version 2 of its extension API. If you want to make use of it then you need to explicitly enable that by implementing JEAFGeneratorExtensionAPI.ext and return 2 as supported version.

Links

For further information please refer to our documentation:

• JEAF Generator Website
• UML Modeling Guide
• Developer Guide

Version 1.27.5 (2025-12-11)

New Features / Improvements

• Make function functions::Class.getSubclasses(...) public (#638)

Migration

Version 1.27.x

• No special actions needed

Version 1.26.x or earlier

• Upgrade of JEAF Generator Meta Model (JMM)
  Due to implementation of #576 changes in JMM were necessary. Before switching to version 1.27.0 please upgrade your UML models to JMM Version 2.7.0 (revision #269 or #69 in MagicDraw Teamwork Cloud)
  
  
• JEAF Generator Extension API v2
  JEAF Generator now also supports a new version 2 of its extension API. If you want to make use of it then you need to explicitly enable that by implementing JEAFGeneratorExtensionAPI.ext and return 2 as supported version.

Links

For further information please refer to our documentation:

• JEAF Generator Website
• UML Modeling Guide
• Developer Guide

Version 1.27.4 (2025-12-01)

New Features / Improvements

• Performance improvements for Maven multi-module builds (#632)
  
  Added special support for Maven multi-module projects. Using this kind of configuration can speed up Maven build time by about 40%.
  
  For further details please have a look on description for configuration parameter useMultiModuleWorkflow on https://www.jeaf-generator.io/developer-guide/maven-plugin-configuration/

Migration

Version 1.27.x

• No special actions needed

Version 1.26.x or earlier

• Upgrade of JEAF Generator Meta Model (JMM)
  Due to implementation of #576 changes in JMM were necessary. Before switching to version 1.27.0 please upgrade your UML models to JMM Version 2.7.0 (revision #269 or #69 in MagicDraw Teamwork Cloud)
  
  
• JEAF Generator Extension API v2
  JEAF Generator now also supports a new version 2 of its extension API. If you want to make use of it then you need to explicitly enable that by implementing JEAFGeneratorExtensionAPI.ext and return 2 as supported version.

Links

For further information please refer to our documentation:

• JEAF Generator Website
• UML Modeling Guide
• Developer Guide

Version 1.27.3 (2025-11-25)

New Features / Improvements

• Use ByteBuffer as type for binary data in OpenAPI (#628)

Migration

Version 1.27.x

• No special actions needed

Version 1.26.x or earlier

• Upgrade of JEAF Generator Meta Model (JMM)
  Due to implementation of #576 changes in JMM were necessary. Before switching to version 1.27.0 please upgrade your UML models to JMM Version 2.7.0 (revision #269 or #69 in MagicDraw Teamwork Cloud)
  
  
• JEAF Generator Extension API v2
  JEAF Generator now also supports a new version 2 of its extension API. If you want to make use of it then you need to explicitly enable that by implementing JEAFGeneratorExtensionAPI.ext and return 2 as supported version.

Links

For further information please refer to our documentation:

• JEAF Generator Website
• UML Modeling Guide
• Developer Guide

Version 1.27.2 (2025-11-13)

Fixed Bugs

• Orphaned OpenAPI types cause StackOverflowError in checks (#618)

Migration

Version 1.27.x

• No special actions needed

Version 1.26.x or earlier

• Upgrade of JEAF Generator Meta Model (JMM)
  Due to implementation of #576 changes in JMM were necessary. Before switching to version 1.27.0 please upgrade your UML models to JMM Version 2.7.0 (revision #269 or #69 in MagicDraw Teamwork Cloud)
  
  
• JEAF Generator Extension API v2
  JEAF Generator now also supports a new version 2 of its extension API. If you want to make use of it then you need to explicitly enable that by implementing JEAFGeneratorExtensionAPI.ext and return 2 as supported version.

Links

For further information please refer to our documentation:

• JEAF Generator Website
• UML Modeling Guide
• Developer Guide

Version 1.27.1 (2025-11-04)

Fixed Bugs

• Extensible enum with dynamic literals causes compile error (#612)

Migration

Version 1.27.x

• No special actions needed

Version 1.26.x or earlier

• Upgrade of JEAF Generator Meta Model (JMM)
  Due to implementation of #576 changes in JMM were necessary. Before switching to version 1.27.0 please upgrade your UML models to JMM Version 2.7.0 (revision #269 or #69 in MagicDraw Teamwork Cloud)
  
  
• JEAF Generator Extension API v2
  JEAF Generator now also supports a new version 2 of its extension API. If you want to make use of it then you need to explicitly enable that by implementing JEAFGeneratorExtensionAPI.ext and return 2 as supported version.

Links

For further information please refer to our documentation:

• JEAF Generator Website
• UML Modeling Guide
• Developer Guide

Version 1.27.0 (2025-10-29)

New Features / Improvements

• Improve memory efficiency for readonly properties (#565)
• Custom default operations for service interfaces (#576)
• Add possibility to use Open API Extensions in generated Open API file (#597)
• Highlight required roles in Java and OpenAPI spec (#599)
• CSV export for deprecations (#587)
• CSV export for breaking changes (#588)

Fixed Bugs

• Compile error for extensible enum without literals (#571)
• Upgrade to version 1.26.x breaks code generation for "publicObjectView" (#598)
• Broken template binding leads to NullPointerException in code generator (#579)
• Need for custom header filter not detected in case of parent interface (#583)
• JSON Subtypes annotation contains ignored class (#572)
• @JsonAlias annotation also generated for BeanParams which make use of backward compatibility settings
  (#566)

Migration

Version 1.26.x or earlier

• Upgrade of JEAF Generator Meta Model (JMM)
  Due to implementation of #576 changes in JMM were necessary. Before switching to version 1.27.0 please upgrade your UML models to JMM Version 2.7.0 (revision #269 or #69 in MagicDraw Teamwork Cloud)
  
  
• JEAF Generator Extension API v2
  JEAF Generator now also supports a new version 2 of its extension API. If you want to make use of it then you need to explicitly enable that by implementing JEAFGeneratorExtensionAPI.ext and return 2 as supported version.

Links

For further information please refer to our documentation:

• JEAF Generator Website
• UML Modeling Guide
• Developer Guide

Version 1.26.9 (2025-09-23)

Fixed Bugs

• Java 25 compatibility issue for usage of BigDecimal in generated code (#580)

Migration

Version 1.26.x

• No special actions needed

Version 1.25.x or earlier

• Upgrade of JEAF Generator Meta Model (JMM)
  Due to implementation of #412 changes in JMM were necessary. Before switching to version 1.25.0 please upgrade your UML models to JMM Version 2.6.0 (revision #266 or #66 in MagicDraw Teamwork Cloud)
  
  
• Upgrade custom template for Service interfaces
  In case that you make use of extension point for service interfaces (jeafgenerator\api\ServiceInterfaceExtensionPoint.xpt) then you need to add the following empty template. This is necessary due to #496

«DEFINE GenerateDefaultImplementation(boolean reactive) FOR Operation»
«ENDDEFINE»

Links

For further information please refer to our documentation:

• JEAF Generator Website
• UML Modeling Guide
• Developer Guide