Update mechanism
(MAGNOLIA-1602)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | updatemechanism |
| Affects Version/s: | None |
| Fix Version/s: | 3.5 RC3 |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Description |
|
With the new update mechanism's ModuleVersionHandler, we have a getInstall() method. It seems a good default behaviour for this would be to reproduce how modules were installed with 3.0 : bootstrapping /mgnl-bootstrap/moduleName/**. Modules will still have the possibility to potentially add more tasks to this. |
| Comments |
| Comment by Magnolia International [ 17/Jul/07 ] |
|
basic solution is started. bootstraps files. |
| Comment by Magnolia International [ 10/Dec/07 ] |
|