It's possible to have a Java2Swift configuration file where multiple Java classes (say, from different packages) mapped to the same Swift type name in the same module. This will cause hard-to-diagnose build failures about there being multiple producers for the same object file.
We should detect this case in Java2Swift itself and produce a reasonable diagnostic with a suggestion of how to fix the problem.
It's possible to have a Java2Swift configuration file where multiple Java classes (say, from different packages) mapped to the same Swift type name in the same module. This will cause hard-to-diagnose build failures about there being multiple producers for the same object file.
We should detect this case in Java2Swift itself and produce a reasonable diagnostic with a suggestion of how to fix the problem.