[MGNLMIGRATION-22] Add Shop module to the main migration process Created: 11/May/12  Updated: 23/Jul/12  Resolved: 14/May/12

Status: Closed
Project: Migration 4.4 to 4.5 (closed)
Component/s: None
Affects Version/s: 1.1
Fix Version/s: 1.1.1

Type: Task Priority: Neutral
Reporter: Eric Hechinger Assignee: Eric Hechinger
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLMIGRATION-26 PostMigrationProcessing must be refac... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

Add the shop module to the migration process.

Shop migration should be part of the main migration process (STK) due to the Script logic. If we perform first the STK migration and then the Form migration, we lost all references of the migrated templates and we are no more able to rename the templates/areas....
So like for Form migration, we have to perform this migration at the same time as STK.

Like for Form, PUR,... let the shop module be migrated and configured by the main migration process.

Add a specific ExtraShopTasks.groovy file that will handle the areas references.
Add options for this module in the Configuration.groovy file
Add sections that handle the specific Shop migration steps in the ConfiguredMigration.groovy file.



 Comments   
Comment by Eric Hechinger [ 14/May/12 ]

First impl Done

Generated at Mon Feb 12 10:16:25 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.