[MULTISITE-168] Use JcrSiteManager instead of DefaultSiteManager Created: 11/Jan/23  Updated: 23/Oct/23  Resolved: 17/Jan/23

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

Type: Improvement Priority: Neutral
Reporter: Marek Strucka Assignee: Marek Strucka
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:
Relates
relates to MGNLSITE-164 Rename DefaultSiteManager to JcrSiteM... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MULTISITE-169 Implementation Sub-task Completed Marek Strucka  
MULTISITE-170 Review Sub-task Completed Jaroslav Simak  
MULTISITE-171 PiQA Sub-task Completed Jaroslav Simak  
MULTISITE-172 QA Sub-task Completed Dai Ha  
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
[X]  Architecture Decision Record (ADR)
Epic Link: DevX Bucket
Sprint: DevX 28
Story Points: 1
Team: DeveloperX
Work Started:

 Description   

We are slowly deprecating DefaultSiteManager and created a JcrSiteManager in the SITE-164

We therefore should make use of the JcrSiteManager instead of the DefaultSiteManager in multisite-jcr too.


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