[MGNLCT-247] Move JCR implementation to a separate submodule Created: 29/Jul/22  Updated: 10/Jan/23  Resolved: 03/Aug/22

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

Type: Task Priority: Neutral
Reporter: Jaroslav Simak Assignee: Jaroslav Simak
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: 0.75d Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
documentation
to be documented by MGNLCT-344 DOC: New module structure in v2 Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLCT-248 Implementation Sub-task Completed Jaroslav Simak  
MGNLCT-249 piQA Sub-task Completed Oanh Thai Hoang  
MGNLCT-250 QA Sub-task Closed Oanh Thai Hoang  
MGNLCT-251 Review Sub-task Completed Oanh Thai Hoang  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: SaaS TPR - ContentTypes
Sprint: DevX 15
Story Points: 5
Team: DeveloperX

 Description   

We already provide submodule with Norsu related classes.

The base content types module still however contains JCR related implementation classes.

Goal is to extract the JCR implementation to a separate submodule, like we did for Norsu.


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