MapStruct 1.4.0.Final is out

Long overdue it is our pleasure to announce the final version MapStruct 1.4. This is our 4th release since november 2015.

Besides bug fixes, the 1.4 release brings some new exciting features:

  • Making use of constructor arguments when instantiating mapping targets
  • Support Gradle incremental annotation processing feature
  • Map nested bean properties to current target
  • Support value mapping between String and Enum
  • Support @Mapping in meta annotations
  • User control over mapping features (direct, method, conversion, 2step)
  • Support mapping from / to Java 14 records (preview feature)
  • New EnumTransformationStrategy and EnumNamingStrategy SPIs
  • Improve performance for 2 step mapping methods

For more details checkout the individual release announcements for the Beta1, Beta2, Beta3 and CR1 releases.

What’s inside

First and foremost as we promised in the 1.3.0.Final release we have delivered the ability to cope with creating beans via constructors. Here it is included mapping into Kotlin Data Classes and Java 14 records. Apart from that we also have the following new features / enhancements:

  • Support Gradle incremental annotation processing - MapStruct will no longer cause an entire recompilation of your java module
  • Map nested beans to current target - i.e. you can use “.” in Mapping#target to map nested beans to the current target
  • Supporting value mapping between String and Enum - i.e. @ValueMapping can be used to map enums into strings and vice versa
  • Supping meta annotations wih @Mapping - i.e. you can create your own annotation that holds common @Mapping definitions
  • User control over mapping features - i.e. you can decide which steps MapStruct should execute during the mapping, meaning that you can easily define clone methods without the need to define mappings for your entire object structure
  • New SPIs for enum mapping

In total 105 issues have been fixed between the 1.3.0.Final and 1.4.0.Final releases. It is interesting that the number of fixed issues is the same as between the 1.2.0.Final and 1.3.0.Final release (this is not on purpose :)).

What’s next

We have said numerous times that we want to do more smaller and more frequent releases. However, every time we say that something else comes up and we still take our time between releases. This is mostly because we are doing this in our spare time.

We will try to do the releases more frequently. There are already some interesting feature requests that we would like to include in some of the future releases.

Most notable requests are:

  • Conditional mapping (i.e. use custom methods to check whether a value is present, think whether string is not blank). There is already a PR from the community about this issue, so this will most likely be the basis for the 1.5 release
  • Mapping into / from Map like structures from / into beans

In case you have some other ideas please feel free to share them with us or vote for issues that you’d like to see implemented in our issue tracker. We are also always looking for new contributors, so if you are interested in helping us out please have a look at our issue tracker or contact us.


We are very proud and thankful of our growing community. It is really satisfying to see how everyone helps each other in our Gitter Room, on StackOverflow or in our Google group. We currently have 3100+ stars and 70+ contributors on GitHub. More than 16000 people are using our IntelliJ plugin, which is already released with support for the new constructor mapping.

Most impressive though are the download numbers we get from the Maven Central repo. As an example here are the numbers for the org.mapstruct:mapstruct-processor artifact:

The number of Downloads compared to the time we released 1.3.0.Final has been quadrupled.


Last but not least we would like to congratulate all the enthusiastic MapStruct contributors making this release possible. In alphabetic order this are all the contributors that contributed to the 1.4 release of Mapstruct:

Happy coding with MapStruct 1.4!!


You can fetch the new release from Maven Central using the following GAV coordinates:

Alternatively, you can get ZIP and TAR.GZ distribution bundles - containing all the JARs, documentation etc. - from GitHub.

If you run into any trouble or would like to report a bug, feature request or similar, use the following channels to get in touch:

comments powered by Disqus