From 7c4e2963a7041c6a38d092e489c5436b75a32245 Mon Sep 17 00:00:00 2001 From: Arjan Vlek Date: Fri, 21 Jun 2019 15:35:08 +0200 Subject: [PATCH] v3.1.0 --- CHANGELOG.md | 5 ++++- pom.xml | 2 +- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 08ea9a96..70472421 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,6 +5,9 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html). ## Unreleased +## [3.1.0] - 2019-06-21 +### Added +- Added value alias for `@BeanProperty` annotation, so using `name =` is no longer needed. It is still supported to maintain backwards compatibility ## [3.0.1] - 2018-07-19 ### Fixed @@ -69,4 +72,4 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0. ## [1.0.0] - 2017-10-04 ### Added -- Issue [#75](https://github.com/42BV/beanmapper/issues/75), **Optional strict handling of BeanMapper mappings**; two layers of protection have been introduced. The first is the possibility to register a class pair with one side being strict. The strict side must have matching properties for all its valid properties. If properties are not matched, an exception will be thrown detailing the mismatches. The second layer of protection works on the Form/Result convention. It checks whether the source is consider a form Ie, classname has the suffix 'Form') or a target is a result (ie, classname has the suffix 'Result'). If this is the case, the other side must have matching properties as well. This second layer of defense works runtime right before the mapping takes place. Note that the suffix can be changed and the convention for strict mapping can be disabled. \ No newline at end of file +- Issue [#75](https://github.com/42BV/beanmapper/issues/75), **Optional strict handling of BeanMapper mappings**; two layers of protection have been introduced. The first is the possibility to register a class pair with one side being strict. The strict side must have matching properties for all its valid properties. If properties are not matched, an exception will be thrown detailing the mismatches. The second layer of protection works on the Form/Result convention. It checks whether the source is consider a form Ie, classname has the suffix 'Form') or a target is a result (ie, classname has the suffix 'Result'). If this is the case, the other side must have matching properties as well. This second layer of defense works runtime right before the mapping takes place. Note that the suffix can be changed and the convention for strict mapping can be disabled. diff --git a/pom.xml b/pom.xml index 8837278a..64e37c33 100644 --- a/pom.xml +++ b/pom.xml @@ -3,7 +3,7 @@ io.beanmapper beanmapper - 3.0.1 + 3.1.0 jar 42 Bean Mapper Easy-to-use bean mapper for conversion from form to object to view