We are currently using OpenMRS version 1.12. I am wondering the best way to handle duplicate libraries with different versions across modules when one of the modules is not developed by our group? For example:
Module A includes library-A-version2.0 (developed by our organization) in the lib folder Module B includes library-A-version1.0 (developed by some other organization) in the lib folder
I see that OpenMRS allows modules to use different versions of the same library that OpenMRS may already include. However, in regards to the same library being included in multiple modules, it looks like the OpenmrsClassLoader gets a set of ModuleClassLoader objects that contain the package of the class name that needs to be loaded. The example above would have both class loaders in the set if I am understanding the code correctly, which could then result in the class being loaded from the wrong module.
What is the best way to handle this situation? We want to use the latest version of the library, but the other module includes an older version.
Thanks, David Ely Software Developer Children’s Health Services Research IU School of Medicine Phone: 317-278-1642 Email: email@example.com