[MGNLETK-92] port update pom dependency & version handler in order to use the new migration process from 2.0.x Created: 30/Nov/12  Updated: 15/Jul/13  Resolved: 30/Nov/12

Status: Closed
Project: Extended Templating Kit (closed)
Component/s: None
Affects Version/s: 2.0.6
Fix Version/s: 2.5

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-117 Migrated Modules configuration: ETK Closed
is related to MGNLETK-87 Update pom dependency & version handl... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

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

If a Magnolia instance is updated from 4.4.6 to 4.5.7, the version handler (DeltaBuilder.update("2.0", "")) will take care of the migration of the module.
If a Magnolia instance was already updated let say from 4.4.6 to 4.5.6 (Version 2.0.6 of the ETK 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.
This is exactly what we expected.

Add dependency to the migration module into the module descriptor of ETK.


Generated at Mon Feb 12 01:48:24 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.