It’s with great happiness and excitement that I’m announcing that Filip Hrisafov is taking over the role of MapStruct’s project lead!
Really that’s just manifesting the status quo of the last couple of months, during which Filip already was acting in that role effectively.
As I’ve been able to contribute less and less time towards MapStruct over the last year,
it was about time to pass on the baton to a new lead,
with many fresh ideas and a great level of enthusiasm.
Filip joined the team in 2016, sending in a patch for improving our test suite.
Since then, he became an invaluable member of the MapStruct community.
He implemented several new features and stepped up to help with reviewing
pull requests, providing help to new contributors, answering related questions on StackOverflow and even doing the last few releases of the project.
Having had the pleasure of working with Filip over the last years, I’m convinced that going forward he’s the perfect person for leading the project.
I am very happy to announce the first version of the MapStruct IntelliJ IDEA plugin.
Now we have official support for 2 IDEs, Eclipse being the first IDE for which we had support from earlier (plugin here).
With the power of IntelliJ you now get completions in @Mapping and @ValueMapping annotations (also for nested mappings ;)).
Apart from that you also get support for: finding usages of methods directly within annotations,
going to declarations from annotations, highlighting support within annotations and refactoring support.
I’m very happy to announce the second candidate release of MapStruct 1.2!
The CR2 release mostly provides bug fixes and other smaller improvements since the CR1,
e.g. related to the handling of mappingInheritanceStrategy (issue #1255).
Further fixes concern the handling nested target properties (#1269).
I’m very happy to announce the first candidate release of MapStruct 1.2!
The CR1 release mostly provides bug fixes and other smaller improvements since the Beta 3,
e.g. related to the handling of the @ObjectFactory annotation (issues #1131 and #1242).
Further fixes concern the handling of imports in the generated code (#1227, #543) and the error reporting in case of incorrect mapper definitions (#1150, #1185).