This changes fixed issue #45
Add failed test case for issue45
Fix issue45 for mapper aware converters + fix problem with using cach…
…ed instances in case of existed destination object
Fix travis tests
Why extract a separate test case class?
@buzdin Because tests from this test case test only static method and the are not required any prepared startup method to create a mapping processor. I usually separate such suites. If you think that it should be one test case - I can merge them.
I usually maintain strict class/test naming convention for unit tests. This helps to switch between code and tests easily. The best option would be to refactor MappingProcessor and extract static methods to separate class, which will result in a separate test case as well. Please do merge them back for now.
I would not use issue numbers in the code since issue trackers come and go, but Dozer remains :)
Would be great to change to meaningful names instead (even if they are long)
Ok, no problem.
This would be great as a separate change list as not directly related, but no problems.
I agree. You can fix it in master and I merge your changes to my branch if you wish.
No need for that. Just have to remember to write it in release notes and close according issue.
Fix tests naming
MappingProcessorStaticTest join into MappingProcessorTest
"issue45Converter" naming change