On 05/11/2015 10:49, Frank Yuan wrote:
:
Generally, m2@1 and m2@2 are different versions of a same component. So 
essentially a module M cannot read duplicate types/modules, except only use 
reflection to access, right?

Yes, assuming m2@1 and m2@2 export the same package to M then it should be caught when attempting to create the Configuration. And yes, M can use the reflection API to read any other module at run-time.

-Alan.

Reply via email to