#3 and #4 create map and inferable mapping methods for public usage

> > No, I changed that for the used mapper fields. But still, the order should remain stable here as well.
> 
> Sorry.. I lost you a bit here. What do you mean?

At some point in the commit history, the order class attributes for the used mappers was determined by the iteration through a HashSet. That caused the generated code to change from time to time without having actual changes. That's what I meant and I think I solved it the very same way you did now at this place. If we find more places like that it might make sense to create our own implementation of ListOrderedSet (as in commons-collections)...