[MGNLPUR-73] 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: | Magnolia Public User Registration |
| Component/s: | None |
| Affects Version/s: | 1.4.1 |
| Fix Version/s: | 1.4.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: |
|
||||||||
| 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 [ 26/Nov/12 ] |
|
The task says "update pom dependency for migration module. But also form module version is updated. Why? And again we are adding update task to the version that was previously released. You need to document why we do it and why it will not cause any side effects. One more thing I've noticed - when adding dependency to migration module, you are not adding dependency to module descriptor. Is this ok? Does it really not matter whether migration module is installed before or not? |
| Comment by Eric Hechinger [ 30/Nov/12 ] |
|
Form update is my mistake. As we are not using new Form features we should keep the previous version. Add a migration task in the version handler in order to migrate the PUR 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. |