[MGNLSITE-131] Make module JCR agnostic Created: 07/Jun/22  Updated: 15/Feb/23  Resolved: 16/Aug/22

Status: Closed
Project: Magnolia Site Module
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0.0

Type: Story Priority: Neutral
Reporter: Milan Divilek Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MULTISITE-134 Make module JCR agnostic Closed
Issue split
split to MTE-141 Fix issue related to Pages rendering ... Closed
Relates
relates to MGNLSITE-150 Support site module on Norsu Closed
dependency
is depended upon by MULTISITE-123 As a developer, i want the site defin... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLSITE-145 Implementation Sub-task Completed Milan Divilek  
MGNLSITE-146 Review Sub-task Completed Rishab Dhar  
MGNLSITE-147 preintQA Sub-task Completed Rishab Dhar  
MGNLSITE-148 QA Sub-task Completed Chuong Doan Huy  
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: Site on 6.3 and SaaS
Sprint: DevX 15, DevX 16
Story Points: 8
Team: DeveloperX

 Description   

Site module heavily depends on JCR, but we need to make it compatible also with Norsu.
We need to make module JCR agnostic.

Possible solutions:

  • separate submodules (one for Norsu, one for JCR)
  • guice provider which decide which implementation to use

Generated at Mon Feb 12 07:13:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.