PropertyMapping added to TypeMap ignored when mapping a structure about modelmapper HOT 8 CLOSED

Yea, if you could post/attach/e-mail a JUnit test that would be great.

from modelmapper.

E-Mail sent. Could not attach it here.

from modelmapper.

Maybe fixed in versions > 0.5.4

from modelmapper.

The test actually passes for me with versions >= 0.4.0

from modelmapper.

Hmm, how could that be?

I am using JDK 1.7.11, Modelmapper 0.5.4 and JUnit 4.8.1.

Could you send me your running version of the test back? If you run it in eclipse or whatever IDE, please send me the whole code project.

from modelmapper.

Not sure - Mailed you my test project though.

from modelmapper.

It turned out I imported the User class from another package. Thus mapping did not apply. Thank you four your support.

However, this brings us to the problem I analysed before I ran into the failing test. It appears that the order in which type maps are created affects mapping.

Lets assume I create the following type map:

createTypeMap(ProjetType, Project)
createTypeMap(UserType, Person)

And now lets assume I change ordering as follows:

createTypeMap(UserType, Person)
createTypeMap(ProjetType, Project)

Mapping results shall be the same (in my opinion) but actually they are not. I modified the test and sent it back to you. Would be nice if you could take a look at it. And give some feedback.

from modelmapper.

Thanks for the followup. This is a known issue that indeed has to do with the order in which TypeMaps are created. See issue #25. This is a high priority for me to fix next, but for now I'll close this issue.

from modelmapper.