Strict strategy break by addMapping about modelmapper HOT 5 CLOSED

A note on the problem with your tests - you may need to create new ModelMapper instances for different tests if the mappings from one test interfere with those from another.

Looking into the broader issue...

from modelmapper.

Hi Jonathan,
thanks for your support.

Is testing project I sent to you suitable, or will be better to try make it
more simple and able to publish?

Jan

2012/11/8 Jonathan Halterman [email protected]

A note on the problem with your tests - you may need to create new
ModelMapper instances for different tests if the mappings from one test
interfere with those from another.

Looking into the broader issue...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/19#issuecomment-10172250.

from modelmapper.

The test project works well. Still looking at the issue...

from modelmapper.

Feel free to give the latest build a try and let me know if you're still having problems. I plan to cut a release with this fix in the next day.

from modelmapper.

Hi Jonathan,
thanks for your fixes. Actual version of modelmapper works much better in
our project. Issue with badly cached mappings between mapping runs seems to
be fixed too now.
But in scenario, where we use a provider, which builds destination property
of dynamic type (context dependent on actual source), we are still using a
small "hotfix". I send the hotfix as a attachment. I try to make a test for
demonstration in spare time tomorrow.

thanks again
Jan

2012/11/17 Jonathan Halterman [email protected]

Feel free to give the latest build a try and let me know if you're still
having problems. I plan to cut a release with this fix in the next day.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/19#issuecomment-10469536.

from modelmapper.