[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: |
|
||||||||
| 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.... 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. |
| Comments |
| Comment by Eric Hechinger [ 14/May/12 ] |
|
First impl Done |