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

[T3rm1]

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.