Implement the new Resources app (MGNLRES-140)

[MGNLRES-168] Move new resources app config back to JCR Created: 18/Jun/15  Updated: 29/Mar/22  Resolved: 26/Jun/15

Status: Closed
Project: Magnolia Resources Module
Component/s: app
Affects Version/s: None
Fix Version/s: 2.4

Type: Sub-task Priority: Neutral
Reporter: Ilgun Ilgun Assignee: Ilgun Ilgun
Resolution: Fixed Votes: 0
Labels: platform-cell, resources-app
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLCAMPU-30 Adapt Campaign publisher to be compat... Closed
Template:
Date of First Response:
Sprint: 5.4 Sprint 4
Team: Nucleus

 Description   

Moving new resource app config from YAML to JCR.
This is necessary because we want to let users extend app functionality (e.g. add actions) without modifying the existing modules.



 Comments   
Comment by Ilgun Ilgun [ 19/Jun/15 ]

Changes can be found in the branch feature/move-to-jcr-config

Comment by Ilgun Ilgun [ 23/Jun/15 ]

Reverted the formatting.

Comment by Philip Mundt [ 25/Jun/15 ]

Small issues related to going back to the JCR config:

  • Bootstrap file has the old module name; should be resources-app
    • From config.modules.resources.apps.resources.xml
    • To config.modules.resources-app.apps.resources.xml
  • When renaming the bootstrap file to its appropriate name, the task that is moving and renaming the old app will actually rename the new app rendering it "useless"
    • See info.magnolia.resources.app.setup.UpdateResourcesAppConfigurationTask
Comment by Philip Mundt [ 25/Jun/15 ]

Fixed on branch MGNLRES-168. Fix involves removing node /modules/resources/apps without checking if there are more than the expected "old/legacy" app named resources in there.

Generated at Mon Feb 12 06:48:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.