Update mechanism improvements (MAGNOLIA-5529)

[MAGNOLIA-3258] installation/update: execute tasks after a later installation of an optional module Created: 23/Jul/10  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: modulemechanism
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Major
Reporter: Philipp Bärfuss Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MAGNOLIA-2979 workflow should not depend on the sam... Closed
is depended upon by MGNLSTK-649 User 'eric' is not able to read workf... Closed
relation
is related to MAGNOLIA-2106 update: support phases (before, after... Closed
Template:
Date of First Response:

 Description   

In several place we define installation tasks which should only be executed if a certain module is installed. This is currently possible by using IsModuleInstalledOrRegistered.

example: workflow module changes the dms configuration on installation

The problem is, that if a module is marked as being optional (dms), it can be installed at a later moment long after the installation tasks of the module (workflow) where executed.

The solution would be to register this kind of tasks explicitly as being dependent on an other module and execute them only after the installation of the module.

Note: we also started to introduce so called bridge modules which only deliver the tasks executed in such a scenario. While it complicates bundling and other things it is still likely that one forgets to install the bridge module.



 Comments   
Comment by Magnolia International [ 13/Aug/13 ]

The solution described here would require changes to how tasks are registered, and might make it quite hard (harder!) to maintain versions/compatibility.
Bridge modules are a simpler solution, but they indeed suffer from discoverability. An app finder/store might alleviate that problem by providing "suggestions".

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.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:44:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.