[MGNLUI-2775] Migrate configuration due to changes required by jcr-agnostic-content-app Created: 27/Mar/14  Updated: 10/Apr/14  Resolved: 10/Apr/14

Status: Closed
Project: Magnolia UI
Component/s: configuration
Affects Version/s: None
Fix Version/s: 5.3

Type: Task Priority: Neutral
Reporter: Christoph Meier Assignee: Aleksandr Pchelintcev
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: JCR-agnostic content apps migration
Sprint: 5.3 Sprint 5, 5.3 Sprint 6

 Description   

Introduction of "Jcr-agnostic-content-app" includes some changes which require to move some configuration within conten-apps.
Migration includes (currently):

  • ChangeAvailabilityRuleClassesTask
  • MigrateAvailabilityRulesTask
  • MigrateJcrPropertiesToContentConnectorTask

Make sure that migration works also when somebody comes from 4.5,



 Comments   
Comment by Christoph Meier [ 27/Mar/14 ]

Copied comment form Eric from MGNLUI-2760

ContentAppModuleVersionHandler calls MigrateJcrPropertiesToContentConnectorTask --> that migrate nodeTypes...

Issue is that ContentAppModuleVersionHandler run before AdmincentralModuleVersionHandler!
There you have update task like

(.addTask(new NewPropertyTask("Set main node type in configuration app as strict", "Sets main node type as strict, i.e. its substypes won't be included in list and search views.", RepositoryConstants.CONFIG, "/modules/ui-admincentral/apps/configuration/subApps/browser/workbench/nodeTypes/mainNodeType", "strict", true)))

that try to handle property into this area..

Comment by Christoph Meier [ 09/Apr/14 ]

Now every content-app is taking care for its migration; see MGNLUI-2781.

Comment by Aleksandr Pchelintcev [ 10/Apr/14 ]

The described task was completed in MGNLUI-2760.

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