[MGNLCT-14] Content Types module 0.5 prevents Magnolia from starting on 5.6 Created: 19/Oct/17  Updated: 27/Oct/17  Resolved: 26/Oct/17

Status: Closed
Project: Content Types
Component/s: None
Affects Version/s: 0.5.1
Fix Version/s: 0.5.2

Type: Bug Priority: Neutral
Reporter: Mikaël Geljić Assignee: Maxime Michel
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Basel 119
Story Points: 5

 Description   

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

Generated at Mon Feb 12 00:36:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.