Uploaded image for project: 'OpenMRS Core'
  1. OpenMRS Core
  2. TRUNK-1996

Module classpaths, classloading should be 100% independent

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Non-Essential
    • Resolution: Won't Fix
    • None
    • None
    • None
    • High

    Description

      I've run into two instances in the last couple of months of modules failing to load (or intermittently loading) due to having different versions of the same jar bundled into the omod. For OpenMRS 2.0 maybe, would it be possible to have complete module classpath, classloader independence.

      The module incompatibilities were sync and namephonetics (i rewrote a couple sections of namephonetics to work around this), and now metadatasharing and formimportexport.

      Gliffy Diagrams

        Attachments

          Activity

            People

              Unassigned Unassigned
              dthomas Dave Thomas
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: