[MGNLFORM-138] Update Pom dependency & Version Handler in order to use the new migration process Created: 19/Oct/12  Updated: 02/Dec/12  Resolved: 30/Nov/12

Status: Closed
Project: Magnolia Form Module
Component/s: None
Affects Version/s: 1.4.3
Fix Version/s: 1.4.4

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:
relation
is related to MGNLMIGRATION-119 Migrated Modules configuration: FORM Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Add dependency on the POM to the migration module.
Create a new version handling task in order to migrate configuration.
Add an Extra Migration sub Task (Post Migration specific task).



 Comments   
Comment by Jan Haderka [ 26/Nov/12 ]
  • you are adding update task to version 1.4 in version 1.4.4. Is this correct? When someone updates from say 1.4.2 to 1.4.4, this task will never get executed. Is this alright? If so it needs to be documented and explained why it's ok.
  • migration module dependency is not defined in module descriptor, so the installation order will be random. Is this ok? If so, pls make sure it's documented in the ticket.
  • new bootstrap file was added to mgnl-bootstrap but it is not bootstrapped manually during update. How is this configuration change then handled on update?
Comment by Eric Hechinger [ 30/Nov/12 ]

Add a migration task in the version handler in order to migrate the FORM module from 4.4.6 to 4.5.7 and higher.
Magnolia 4.4.6 shipped FORM 1.3.2
Magnolia 4.5.0 shipped FORM 1.4

If a Magnolia instance is updated from 4.4.6 to 4.5.7, the version handler (DeltaBuilder.update("1.4", "")) will take care of the migration of the module.
The migration task will also bootstrap the files defined in mgnl-bootstrap/migration.
If a Magnolia instance was already updated let say from 4.4.6 to 4.5.6 (Version 1.4.3 of the FORM module) and we want now to update to Magnolia 4.5.7, in this case, the version handler's will not run the migration.
Migration already took place during update from 4.4.6 to 4.5.6. and should not run again. Bootstrap files defined under mgnl-bootstrap/migration where already handled during the migration for 4.4.6 to 4.5.6. They shouldn't be bootstrapped again.
This is exactly what we expected.

Generated at Mon Feb 12 05:37:14 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.