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.