rvjansen
commented
2 years ago Comment by Kermit Kiser [ 07/Jun/15 ] This seems like a reasonable request but I am not sure if it can be implemented. The classes are not ambiguous until the customer refers to them in an ambiguous way . The translator quits as soon as an ambiguity is detected. I t does not continue to check for more clashes.
When a class reference is ambigous , a rather incomplete error message is given. It would be really helpful when the proper error message would be succeeded by a list of the complete class names which be displayed :(when possible). Without that improvement, always all JAR-Files in the classpath must be inspected for the duplicate classnames. Of course, this happens only when not the complete class names, but the short classnames are used in the program.
Thomas Schneider