MapStruct 1.5.4.Final bug fix released
It is my pleasure to announce the 1.5.4.Final bug fix release of MapStruct. This release includes support for Jakarta CDI , 5 bug fixes and a documentation improvement.
It is my pleasure to announce the 1.5.4.Final bug fix release of MapStruct. This release includes support for Jakarta CDI , 5 bug fixes and a documentation improvement.
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:
@Mapping
. Thanks to Myat Min for pointing out this oversight.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.
It is my pleasure to announce the 1.5.3.Final bug fix release of MapStruct. This release includes 18 bug fixes and 7 documentation improvements.
The most notable fixes are around the handling of nested imports and generics handling
It is my pleasure to announce the 1.5.2.Final bug fix release of MapStruct. You might ask yourself, where is 1.5.1. We released that version on 5th of June 2022, 3 days after the 1.5.0.Final release. It had a fix for a bug that was reported by our good friends from JHipster.
This release includes 1 enhancements and 2 bug fixes.
With this release we started supporting Text blocks for all the expressions.
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:
@Generated
annotation is being imported from the correct package for the build environment. This now follows the same logic as the MapStruct Core. Thanks to John Kelly for pointing out this omission.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.