in reply to
Re: Wrong package used when method and package have the same name
in thread Wrong package used when method and package have the same name
Thanks for the information. I guess I should not have called it a minimal test case but simply a reduced test case.
Usually my method names would be lower-case and my package names ucfirst, so the situation would never come up. In this case I was attempting to replace an existing module and retain the same method names, which happened to use this a mixed case capitalization scheme. The duplicate names were introduced when I decided some of the data shouldn't really be stored in the original module, because multiple instances would need to be stored, and the logical name for the holding class was of course the same as the original method name...