[ http://jira.magnolia.info/browse/MAGNOLIA-1853?page=comments#action_15099 ] Fabrizio Giustina commented on MAGNOLIA-1853: ---------------------------------------------
> if the custom module declares a dependency on the cache module, "custom > module" will always be started before "cache module" mh.. shouldn't this be: "custom module" will always be started AFTER "cache module". Cache module should depends from my module in order to obtain this, isn't it? Also consider that I could need to change configuration that is loaded by core, that can easily be done if a single "pre-startup" phase is executed before starting any module > ModuleLifecycle : allow usage of the Task api and global save/rollback > ---------------------------------------------------------------------- > > Key: MAGNOLIA-1853 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1853 > Project: Magnolia > Issue Type: Task > Components: core > Reporter: Grégory Joseph > Assigned To: Grégory Joseph > Fix For: Green > > > This is currently implemented through startupTasks, but using the > ModuleLifecycle is more relevant, since startup tasks are not related to any > given version of a module -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
