[MGNLSTK-1030] Update Demo project in order to Use DAM and no more DMS module. Created: 21/Nov/12  Updated: 11/Feb/13  Resolved: 26/Nov/12

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: demoproject
Affects Version/s: 2.5
Fix Version/s: 2.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:
relation
is related to MGNLDAM-4 Determine and Implement strategy for ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

Update demo project version handler and bootstrap files in order to be linked with the DAM module.
In case of fresh installation,

  • bootstrap demo projects with link to DAM repo
  • Bootstrap binary into the DAM repository
    In case of update,
  • create a new delta registry based on 2.0 that will run DAM migration task.


 Comments   
Comment by Eric Hechinger [ 30/Nov/12 ]

Currently we only have created new bootstrap files for the following repositories:
website/demo-project and demo-features
dms/demo-project.

These bootstrap are already ready to use the new DAM module.

For dms bootstrap file, this is a new file replacing the old dms bootstrap file (original commit e85a812ba1e7126b09e2e7e70f73584a6bb63201)

We initially plane to add to the version handler a migration task responsible to do migrate the current content, but it was decided to change the migration approach for M5.
In M5, modules will be responsible to perform the migration , in this case, the DAM module will have a migration task responsible to migrate the demo-project content.

Generated at Mon Feb 12 07:32:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.