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

Status: Closed
Project: Magnolia Categorization Module
Component/s: None
Affects Version/s: 1.2.3
Fix Version/s: 1.2.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:
dependency
is depended upon by MGNLMIGRATION-121 Migrated Modules configuration: CATEG... 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 ]

Comment in issue says "Add dependency in POM", hell even commit message says so, but only code I see updated is version handler.

Also you are editing code that will be released as 1.2.4, but adding version in version handler as 1.2. Are we sure that there are no side effects? It means that anyone updating from 1.2.3 will NOT get such task executed. Is that correct? Should be described in the issue as it is for sure not ordinary way of handling updates.

Comment by Eric Hechinger [ 27/Nov/12 ]

Add a migration task in the version handler in order to migrate the Categorization module from 4.4.6 to 4.5.7 and higher.
Magnolia 4.4.6 shipped Categorization 1.1.8
Magnolia 4.5 shipped Categorization 1.2.

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.2.3 of the Categorization 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.

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 ]

Modification done.

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