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

Status: Closed
Project: Forum (closed)
Component/s: dialogs, templates
Affects Version/s: 1.3.1
Fix Version/s: 1.3.2

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-120 Migrated Modules configuration: FORUM 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 ]
  • PUR dependency version number was changed as well. Why?
  • Module descriptor doesn't define dependency to migration so the order in which modules will be installed is undetermined.
  • update task was added to version 1.2.2 which was relased BEFORE Magnolia 4.5. First version of Forum released with Magnolia 4.5 was 1.3!!!
Comment by Eric Hechinger [ 30/Nov/12 ]

True
PUR update is my mistake. As we are not using new PUR feature's we should keep the previous version (1.4).
True.
For Forum module shipped with the Magnolia 4.5 release, the minimum version should be 1.3.
The migration task is added to the task handling the 1.3 updates .
Magnolia 4.4.6 shipped Forum 1.2.1
Magnolia 4.5.0 shipped Forum 1.3
In the version handler of Forum we have a DeltaBuilder.checkPrecondition("1.2.1", "1.3")
meaning that the minimal version allowed for performing the migration is 1.2.1 (as the minimal version allowed to perform the migration is version 4.4.6 of Magnolia)

But we also have update task in the version handler for DeltaBuilder.update("1.2.2", "")

So a user having a
Forum 1.2.1 with Magnolia 4.4.6 updating to 4.5.7 will first perform the updates to 1.2.2 and then updates to 1.3 including the migration task
Forum 1.2.2 with Magnolia 4.4.6 updating to 4.5.7 will updates to 1.3 including the migration task

A user that already migrated to 4.5 and now update to 4.5.7 (Forum version 1.3.2) will not run the migration task as they are defined in the version handler for 1.3
This is exactly what we expected.

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