ResourceReference uniques for packages and classes

[nsolov]

Packages and classes are described in module.xml as resources (for example <Resource Name="community.PKG"/>).

When packages are installed, a resource uniqueness check is performed, this check for uniqueness based on the Name attribute (as a string).

This leads to such a situation.

1. If module 1 has <Resource Name="community.PKG"/> and module 2 also has <Resource Name="community.PKG"/> - then the second module will not be installed, even if there are no overlapping classes in this package
2. If module 1 has <Resource Name="community.PKG"/> and module 2 has <Resource Name="community.My.cls"/> - both modules will be installed even if class community.My.cls overwrites the class from module 1.

[isc-tleavitt]

IMO (2) is a problem in IPM, and (1) should still be disallowed. Reason: in an embedded source control setting, each class needs to have a clearly-defined home package.

I recall dealing with (1) before (but likely after the initial ZPM fork from HS PM), and it's possible that the merge from v1 will include a fix. Need to review this.