Classes / enums with same name but different package replace each other

If your project has two or more classes (also enums) with the same name (but different packages) they replace each other during model definition.

public class MyClass {
    private ClassWithSameName classOne;
    private subpackge.ClassWithSameName classTwo;

    // getters and setters
}

There will only be one generated Schema for ClassWithSameName and both properties point to the same definition. Same problem for enums when they are resolved as refs.
I'm aware of useFqn in TypeNameResolver but this setting affects all names. I'd prefer a solution where the name is only changed in case of a collision.

Start with TypeNameResolver and the model-definition path that resolves class and enum references. Reproduce the case with same simple names in different packages, then trace how schemas and refs are assigned. Done means colliding names receive distinct definitions while non-colliding names retain their existing naming behavior.