[MAGNOLIA-7786] Magnolia webapps should have a default content-importer directory Created: 04/May/20  Updated: 17/Dec/20

Status: Selected
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to NPMCLI-238 'mgnl jumpstart' command should also ... Open
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Release notes required:
Yes
Documentation update required:
Yes
Epic Link: Content Importer Obstacles

 Description   

As a developer I want to have a standard, pre configured 'content-importer' directory in the Magnolia webapps, similar to the 'modules' one.

 

Notes:

Magnolia Cloud may also configure the 'content-importer' directory, so please ensure that this change is compatible with the cloud approach.

 

 


Generated at Mon Feb 12 04:26:49 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.