Adding test scenario for the feature of loading objects via constructor without specifying a result map
Tries to find a proper constructor in a object, when the default constructor is not available
Refactoring creation of object to give more useful information when it fails
Organizing code and extracting some methods to be more readable
Tries to create an object matching the constructor, when the default approach fails
Related to #142. Added 'overwrite' option to force JarJar maven plugin to re-compile.
Fixes #167. @One is broken in 3.2.6
Fixes #168. For consistency with XML the property should be called
fetchType() and not lazy().
Fixes #169. Set logging decorator to all caches.
Additional tests for #167.
Failing test for #165
Minor doc changes.
[maven-release-plugin] prepare release mybatis-3.2.7
[maven-release-plugin] prepare for next development iteration
Fixes #165. Do not change the handler for a primitive when changing the
handler for a wrapper.
Corrected DOCTYPE declaration in a test mapper.
Fixes #176. Multiple mybatis instances in the same jvm can produce
ehcache collisions.
Test for handling UUIDs.
Tests resultType before trying to use default object factory to create new instance
Some changes for #184