It is my pleasure to announce the next official release of MapStruct Spring Extensions. What started out as a StackOverflow question turned into its own (sub-)project within the MapStruct organization.

Changes in this release:

• New module test-extensions which contains a @ConverterScan annotation that greatly simplifies the writing of integration tests. Thanks to Joose Haverinen for the suggestion.
• New annotation @AdapterMethodName which allows a developer to override the default name for generated adapter methods. Thanks to pw-lehre for the inspiration.
• New annotation @DelegatingConverter that will generate a converter calling the one whose method is annotated with this. The intended use is in conjunction with MapStruct Core’s @InheritInverseConfiguration. Thanks again to pw-lehre for the idea.

Including the annotations and extensions defined in this project will generate a class acting as bridge between MapStruct’s conventions and Spring’ s ConversionService API that in turn can be added to any Mapper’s uses attribute. See the examples for details.

It is my pleasure to announce the next official release of MapStruct Spring Extensions. What started out as a StackOverflow question turned into its own (sub-)project within the MapStruct organization.

Changes in this release:

• Spring Extensions will now honour the mapstruct.suppressGeneratorTimestamp processor option. Thanks to freund17 for pointing out this omission.

We’re functionally complete. There are currently no plans for further features, although we will keep an eye on compatibility with future MapStruct and Spring releases as well as community requests.

Including the annotations and extensions defined in this project will generate a class acting as bridge between MapStruct’s conventions and Spring’s ConversionService API that in turn can be added to any Mapper’s uses attribute. See the examples for details.

It is my pleasure to announce the 1.5.5.Final bug fix release of MapStruct. This release includes support for Jakarta XML Binding , 1 bug fixes and a documentation improvements.

It is my pleasure to announce the next official release of MapStruct Spring Extensions. What started out as a StackOverflow question turned into its own (sub-)project within the MapStruct organization.

Changes in this release:

• Collection type mappings ignored the generic element type. This was no functional problem as such, but it prevented generating an adapter class for several collection type mappings within the same scope. Thanks to Hypercube Software and coding-guo for pointing this out.

We’re now functionally complete. There are currently no plans for further features, although we will keep an eye on compatibility with future MapStruct and Spring releases.

Including the annotations and extensions defined in this project will generate a class acting as bridge between MapStruct’s conventions and Spring’s ConversionService API that in turn can be added to any Mapper’s uses attribute. See the examples for details.