[MAGNOLIA-8515] Adapt the platform/main norsu feature branch in order to be compatible with jcr Created: 04/Aug/22  Updated: 13/Oct/22  Resolved: 08/Sep/22

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0

Type: Task Priority: Neutral
Reporter: Andrei Ichimescu Assignee: Andrei Ichimescu
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: 0d Remaining Estimate: 0d
Σ Time Spent: 6.25h Time Spent: 6.25h
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by MAGNOLIA-8509 Port TemplateAvailability and MetaDat... Closed
dependency
is depended upon by PAGES-806 [SaaS] Adapt the pages module after m... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MAGNOLIA-8551 QA Sub-task Completed Thuy To  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: TPR SaaS Norsu Pages
Sprint: AuthX 17
Story Points: 3
Team: AuthorX

 Description   

Context:
Some changes that are not backward compatible with the on-prem, have been made to the platform/main norsu branch:
https://git.magnolia-cms.com/projects/PLATFORM/repos/main/browse?at=refs%2Fheads%2Ffeature%2FmagnoliaVersion-6.3-norsu-SNAPSHOT
Ideally the feature branch needs to be merged in master, and when that happens, jcr related operations need to work.
We need, not to overwrite the services, but rather create new ones and ensure that the runtime implementations are either set to jcr (for on-prem) or to norsu (for saas).

Dev Notes: the incompatible changes have been pushed here:
MAGNOLIA-8509


Generated at Mon Feb 12 04:33:24 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.