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

A missing required module should not prevent starting of other modules

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Must
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Platform 2.0.0
    • Component/s: None
    • Labels:
      None
    • Complexity:
      Low

      Description

      When a required module is not started for any module, all modules are not started, including the ones which have all their dependencies started. As a result, the end user does not even have a way of starting the required modules because the legacyui module is not started and yet it is the one with the page to help the end user start the required modules.
      This should be fixed to the state we had before, where the module engine would still go ahead and start other modules which are fine.

        Gliffy Diagrams

          Attachments

            Attachments-Category-Modification

              Activity

                People

                • Assignee:
                  dkayiwa Daniel Kayiwa
                  Reporter:
                  dkayiwa Daniel Kayiwa
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: