installation/update: execute tasks after a later installation of an optional
module
------------------------------------------------------------------------------------
Key: MAGNOLIA-3258
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3258
Project: Magnolia
Issue Type: Improvement
Components: modulemechanism
Reporter: Philipp Bärfuss
Assignee: Boris Kraft
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 bridget 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
