[MGNLSTK-1013] Update Pom dependency & Version Handler in order to use the new migration process Created: 19/Oct/12  Updated: 04/Dec/13  Resolved: 26/Nov/12

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: build
Affects Version/s: 2.5
Fix Version/s: None

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

Issue Links:
dependency
is depended upon by MGNLMIGRATION-116 Migrated Modules configuration: STK Closed
relation
is related to MGNLSTK-1012 Update Pom dependency & Version Handl... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 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 Eric Hechinger [ 26/Nov/12 ]

For this Release, migration is handle by the DAM module. no need to add a specific migration task into the STK module.

Comment by Eric Hechinger [ 30/Nov/12 ]

Dependency to the migration module was changed to enforce dependency to migration module 1.2 in case of installation of STK 2.0.7.

Add a migration task in the version handler in order to migrate the STK module from 4.4.6 to 4.5.7 and higher.
Magnolia 4.4.6 shipped STK 1.4.6
Magnolia 4.5.0 shipped STK 2.0

If a Magnolia instance is updated from 4.4.6 to 4.5.7, the version handler (DeltaBuilder.update("2.0.0", "")) 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 2.0.6 of the STK module) and we want now to update to Magnolia 4.5.7,
in this case, the version handler's will not run the migration task.
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 by the 1.1 Migration module tasks. They shouldn't be boutstrapped again.
This is exactly what we expected.

Generated at Mon Feb 12 07:32:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.