[MGNLRSSAGG-58] 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 RSS Aggregator Module
Component/s: None
Affects Version/s: 1.3.3
Fix Version/s: 1.3.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-123 Migrated Modules configuration: RSS 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 ]

please do not introduce .0 in version numbers. We always skipped them in the past. Adding them now causes issues during releases.

+      <version>1.2.0-SNAPSHOT</version>

And again since you are adding task to previous version you should explain in the ticket why this is necessary and how is ensured that it works with older versions of migration/stk modules and if it is ok if task is skipped during update in case user is updating from rssagg version higher then 1.3. Or if it is not ok to mix this update w/ older versions of stk/migration modules, safeguards need to be added either via module descriptor dependencies or via install condition.

Comment by Eric Hechinger [ 29/Nov/12 ]

Add a migration task in the version handler in order to migrate the RSS module from 4.4.6 to 4.5.7 and higher.
Magnolia 4.4.6 shipped RSS 1.2.2
Magnolia 4.5.0 shipped RSS 1.3

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.3.3 of the RSS 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.

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