Greetings. I asked this question over at the google groups thread and have been wondering why no one in the last year seems to have any interest in the project, lol. Luckily, I finally found this destination.

Sorry for that. I've updated the Google Groups to have a link to the GitHub discussions.

Is it feasible (what will it take) to extend method lookup to include the @Mapper(uses = "OtherClasses") classes?

This would be a rather complex thing to do, since it might lead to a lot of backwards incompatible problems.

What we could accept is to have a way to define multiple configurations that you might be able to use. However, we have to thing about merging those.

My current solution is to use the "experimental" Mapping Composition. Each class being mapped has an equivalent MappingCompositionAnnotation and I "inherit" that way. It works fine.

I would say that this experimental Mapping Composition is way better alternative than the @InheritConfiguration. So I would go with that, even though we say it is experimental. We've named it like that in order to have some leeway in case we needed to change something. However, I think that we can remove that now. I've created #3239 for this