Handling import conflicts with multiple equally named classes/states in different packages

[GoogleCodeExporter]

What steps will reproduce the problem?

If two imported packages contain classes/states with the same name, we don't 
report an error immediately which can lead to weird runtime errors.


What is the expected output? What do you see instead?

The user should get some error. Currently, if the programmer references one of 
the problematic classes/states and the runtime chooses the other one, there'll 
be a lot of "Member 'foo' not found"-like errors. Java handles it like this:
"In rare cases it can happen that you need to reference two classes having the 
same name in different packages. In those cases, you can not use the import 
keyword for both classes. One of them needs to be referenced by typing in the 
whole package name." [Source: 
http://en.wikibooks.org/wiki/Java_Programming/Packages]
We should probably do the same.

Original issue reported on code.google.com by [email protected] on 9 Jun 2010 at 6:43