merging classes with same api path can cause with model resolution

[fehguy]

if you have two classes pointing to the same @Api path, you may have models unable to resolve. Create a class with /v1 as the path with one model as a response type, and another class with the same @Api path. The models may not resolve correctly from one or the other classes.

[pikazlou]

Fixing this issue is important for me. Can you give some thoughts about the class responsible for it. I can then try to fix it.

[pikazlou]

I fixed and checked this issue in my fork of master (1.3.5) branch.
Here is the patch: https://gist.github.com/pikazlou/4d75f0a9aefbd3151011
generated with 'git format-patch -1 ...'
Please note, I have zero experience with scala, so my patch can be improved.

[fehguy]

Great! Can you send a pull request to the develop branch here?

[fehguy]

This should be fixed in 1.3.6