[MGNLDMS-243] Update Pom dependency & Version Handler in order to use the new migration process Created: 19/Oct/12  Updated: 29/Jan/13  Resolved: 29/Nov/12

Status: Closed
Project: Document Management System (closed)
Component/s: None
Affects Version/s: 1.6.4
Fix Version/s: 1.6.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:
dependency
is depended upon by MGNLMIGRATION-122 Migrated Modules configuration: DMS 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 [ 22/Nov/12 ]

The task was added to 1.5.3 version. This is completely wrong! This version was released long before Magnolia 4.5 so there is no way that this would be the right version for performing such migration.

Comment by Milan Divilek [ 29/Nov/12 ]

Migration module dependency is not defined in module descriptor. So if migration module isn't part of webapp magnolia ugly fails during start.

Comment by Eric Hechinger [ 29/Nov/12 ]

True.
For DMS module shipped with the Magnolia 4.5 release, the minimum version should be 1.5.3.
A check precondition is added to the Version Handler. At least version 1.5.3 should be installed (First step of migration:
Update magnolia to version 4.4.6). Once Magnolia is updated at 4.4.6, this instance can be migrated
to 4.5.x.

Also add a migration task in the version handler in order to migrate the DMS module from 4.4.6 to 4.5.7 and higher.
Magnolia 4.4.6 shipped DMS 1.5.3
Magnolia 4.5 shipped DMS 1.6.

If a Magnolia instance is updated from 4.4.6 to 4.5.7, the version handler 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 1.6.4 of the DMS module) and we want now to update to Magnolia 4.5.7, in this case, the version handler's will not run the migration.
This is exactly what we expected.

Generated at Mon Feb 12 00:49:47 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.