-
Sub-task
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
At the moment, if we have a module dependency issue, Magnolia can't be started. Exceptions are reported in the logs. Since the UI is nice enough to report install / update issues, it could just as well handle setup (wrong dependency) issues.
This, like a couple of other improvements, calls for delegating the exception handling to a separate component, possible the ModManUI.
- is related to
-
MAGNOLIA-1855 Update mechanism : better feedback to user
- Closed
-
MAGNOLIA-2743 startup: don't fail to start the system just because a single module/component fails to start
- Closed