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:
It is not necessary anymore to explicitly declare the convert method in the mapper interface if it doesn’t require any Mapstruct core annotations like @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.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:
Mark the Processor as incremental for Gradle Build. Thanks to Olivier Boudet) for raising the original issue.
Make sure the @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.
In line with MapStruct Core 1.5, we have upgraded the build environment to JDK 11.
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.