[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: |
|
||||||||
| 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 ] |
|
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. 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. 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. |