(v3) conflicting packageNameToPlatformPropertiesMap in multiple components can lead to unexpected results ...

[dalehenrich]

In RowanSample9V3Test>>testSpec_0085_04... we're loading a trait from a package referenced by the Tr04 component into RowanSample9_1, However, component Tr04 specifies that RowanSample9_2 should be used... This happens because the lookup algorithm doesn't care about which component triggered the load and different components specify different symbol dictionaries for the same package ...

THIS IS NOT COOL ...

Need a better way to guarantee consistency ...

Use RowanSample9V3 [221d18c9a] (spec_0085)

[dalehenrich]

I've worked around the issue by using a different package name ... so moving to a different package AND symbol dictionary is not a bad way to go ...

At this point, I'm inclined to think it should be an error to have conflicting attributes for the same package ...