Update mechanism (MAGNOLIA-1602)

[MAGNOLIA-1628] Review install mechanism Created: 16/Jul/07  Updated: 23/Jan/13  Resolved: 10/Dec/07

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:
relation
is related to MAGNOLIA-1803 Review file extraction - if/when it i... Closed
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.
to do : extract files, ...

Comment by Magnolia International [ 10/Dec/07 ]
  • Modules extending the DefaultModuleVersionHandler now do the following on install, by default:
    BootstrapEmptyRepositoriesTask, ModuleBootstrapTask, SamplesBootstrapTask, ModuleFilesExtraction, RegisterModuleServletsTask
  • removed some irrelevant/outdated TODOs from the code.
Generated at Mon Feb 12 03:28:46 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.