Update mechanism improvements
(MAGNOLIA-5529)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | modulemechanism, updatemechanism |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Date of First Response: | |||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Magnolia International [ 08/Mar/10 ] |
|
Same goes for an illegal module descriptor. |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |