[MULTISITE-134] Make module JCR agnostic Created: 03/Aug/22  Updated: 15/Feb/23  Resolved: 08/Sep/22

Status: Closed
Project: Magnolia Multisite Module
Component/s: None
Affects Version/s: None
Fix Version/s: 3.0.0

Type: Story Priority: Neutral
Reporter: Milan Divilek Assignee: Robert Šiška
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
clones MGNLSITE-131 Make module JCR agnostic Closed
Relates
relates to MULTISITE-140 Support multisite module on Norsu Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MULTISITE-136 Implementation Sub-task Completed Robert Šiška  
MULTISITE-137 Review Sub-task Completed Jaroslav Simak  
MULTISITE-138 preintQA Sub-task Completed Chuong Doan Huy  
MULTISITE-139 QA Sub-task Completed Jaroslav Simak  
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)
Epic Link: Site on 6.3 and SaaS
Sprint: DevX 16, DevX 18
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 06:06:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.