Version 5.3.0 has been released recently and is available in Maven repository.
The core features in 5.3 are migration to SLF4J and Mapping API.
Mapping API is a new way of describing bean conversions via embedded fluent api. It is significantly better and more elegant to go with API mappings rather than Xml in most of the cases. However I feel that the new approach will require a couple of releases to stabilize and mature. Feel free to try that and provide your feedback in this thread.
There were also done a number of small fixes and improvements. The full list is available in release notes page.
As always we are in lack of resources, who could help the project in many ways. We need proper examples, documentation refresh and about hundred tickets to resolve. This is not an amount of work current team can handle working in part time. However work will go on in any case (just slower). If you are interested in contributing please drop me a mail to buzdin-at-gmail-dot-com.
Stay tuned,
Dmitry Buzdin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Dozer Users,
Version 5.3.0 has been released recently and is available in Maven repository.
The core features in 5.3 are migration to SLF4J and Mapping API.
Mapping API is a new way of describing bean conversions via embedded fluent api. It is significantly better and more elegant to go with API mappings rather than Xml in most of the cases. However I feel that the new approach will require a couple of releases to stabilize and mature. Feel free to try that and provide your feedback in this thread.
There were also done a number of small fixes and improvements. The full list is available in release notes page.
As always we are in lack of resources, who could help the project in many ways. We need proper examples, documentation refresh and about hundred tickets to resolve. This is not an amount of work current team can handle working in part time. However work will go on in any case (just slower). If you are interested in contributing please drop me a mail to buzdin-at-gmail-dot-com.
Stay tuned,
Dmitry Buzdin