MapStruct 1.1.0.CR1 consolodates the functionality introduced in the preceeding MapStruct 1.1.0 Beta releases. A number of bugs were solved:
- Automatic generation of an iterable mapping methods where the property selection is based on a qualfier.
- Collection source getter null check to avoid NullPointExceptions.
- Missing imports for generic types in collections in generated methods.
- Removing redundant code from generated code when using nested source properties.
- Optimisation when using enum constant (using an enum constant instead of a String conversion).
- Fixing order for dependsOn.
- Fixing an issue introduced 1.1.0.Beta2 that causes problems for the @MappingTarget in combination with @InheritInverseConfiguration
It has been a while since the latest release of MapStruct. Via our mailing list, issue list and other channels we have received valuable feedback. We have tried to incorporate some of that feedback into a number of new features.
MapStruct 1.1.0.Beta2 introduces a number of popular requested features, like source presence check and nested target properties.
It has been four months since the release of the first final version of MapStruct. We’ve received a lot of great feedback and noticed a substantial increase of interest in the project. A couple of bugs were reported that we intend to fix with MapStruct 1.1 while also working on new features.
Today we release MapStruct 1.1.0.Beta1, containing fixes for most of the user-reported bugs. But we’ve also added some improvements and prepared for new features:
- The new annotation
@ValueMapping is introduced to be used for
enum mappings. Previously, you would have used
@Mapping for this, but we found a separate annotation makes things more clear and puts us in a better position for some upcoming features. The usage of
enum mappings now triggers a deprecation warning and asks you to use
- The new annotation
@Named is a predefined
@Qualifier that can be used when creating a custom qualifier annotation seems too inconvenient.
- Handling of types with generically typed properties has been improved, so that you can now declare something like
SearchResult<VesselDto> vesselSearchResultToDto(SearchResult<Vessel> vessel).
- The preferred way of configuring the annotation processor in Maven projects has been updated to leverage the latest
annotationProcessorPaths option, which makes the configuration a bit more smooth. Check the updated documentation.
While we pride ourselves on providing a comprehensive and detailed documentation, the MapStruct reference guide grew out of form a bit over time. To name just one issue, readability wasn’t great on smaller screen sizes.
All that’s history now, the reference guide has been converted into the AsciiDoc format, which makes the documentation much easier to maintain and allows for several publishing options using the fantastic AsciiDoctor tool.
The guide is provided in two formats now: HTML and as PDF.
It’s with great pleasure and excitement that I announce the final release of MapStruct 1.0!
MapStruct is a source code generator for efficient, type-safe mappings between Java bean types, based on annotated interface definitions. It works in your command line builds (e.g. via Maven or Gradle) as well as your favourite IDE. The advantages of this approach are manifold:
Great performance: Plain method invocations only, no use of reflection Compile-time type safety: Only objects and attributes actually mapping to each other can be mapped, no accidental mapping of an order entity into a customer DTO etc.