We have some requirement on top down REST api design approach - api designer is able to generate interfaces from spec (or swagger) and there may be multiple versions of the spec implemented simultaneously (preserving backwards compatibility for api consumers). As a result, rs endpoint definition ends up with multiple java interfaces containing resources annotated with @Path.
For the deduplication reason, single implementing class is desired and looking into RestEasy scanner (resteasy 3.0.24, wildfly 11 ) - it only register one interface (first it finds during startup path registration).
Is this scanner behavior intentional for some reason or considered a bug?
