Content Types module 0.5 prevents Magnolia from starting on 5.6+
—namely because of the module dependency to activation, which is now replaced by the new publishing module(s).

Original plan was to shift to CT 1.0 on 5.6. However since CT 1.0 will not be there straight away, Cloud will still have to use 0.5 on 5.6 to begin with.

My proposal is: let's make CT 0.5 work with both 5.5 and 5.6, i.e.

• Make dependency to (old) activation module optional (and provided maven-wise), and update code to treat it as such (MVH to migrate subscribers' config is needed, see MigrateSubscribersTask)
• Verify whether there is anything to do for the (new) publishing module; if so, that would also be through an optional dependency