[MGNLCMNT-71] Update Pom dependency & Version Handler in order to use the new migration process Created: 19/Oct/12 Updated: 06/Dec/13 Resolved: 29/Nov/12 |
|
| Status: | Closed |
| Project: | Commenting (closed) |
| Component/s: | None |
| Affects Version/s: | 1.2.2 |
| Fix Version/s: | 1.2.3 |
| 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: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Add dependency on the POM to the migration module. |
| Comments |
| Comment by Jan Haderka [ 22/Nov/12 ] |
|
In the comment you claim update was to add dependency on migration module, which is fine, but as part of this update you also updated dependencies to forum and STK w/o any explanation on why they need to be updated. Or if they don't need to be updated, then this part of change should be reverted back. |
| Comment by Eric Hechinger [ 27/Nov/12 ] |
|
Add a migration task in the version handler in order to migrate the Commenting module from 4.4.6 to 4.5.7 and higher. If a Magnolia instance is updated from 4.4.6 to 4.5.7, the delta builder responsible for update (1.2) will call the migration task first and then perform the remaining update tasks. If a Magnolia instance was already updated let say from 4.4.6 to 4.5.6 (Version 1.2.2 of the Commenting 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 task is define in the first DeltaBuilder (1.2)). |
| 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. |