Hi,
Attached is a simple example using the LabVIEW DynamicDispatch example as source. The internal package contains the three classes Shape, Triangle and Square. All these classes have a method named Identify.
The public code is supposed to use these three classes internally, but not expose them, hence we add them as an internal dependency.
If the wireflow_lib_wf_internalclasses-1.0.0.1.vip is added as a internal dependency, the build of the public package fails with the error shown in the attached image, if we remove the package from the list of dependencies the public package package builds just fine.
If we monitor the VIPM temp build folder during the build, and if we check other internal packages, we see that the folder where VIPM puts the internal dependencies and adds the name-spacing is a flat structure. Since several methods have the same name it means that they will still have the same name after the name-spacing, resulting in the failed builds
/J
JKI example.zip