[MGNLCI-11] The import directory shouldn't have to be a subdirectory of the resources directory Created: 15/Sep/16  Updated: 09/Feb/17  Resolved: 29/Sep/16

Status: Closed
Project: Content Importer
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Major
Reporter: Christopher Zimmermann Assignee: Ilgun Ilgun
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2016-09-28 at 16.55.04.png    
Issue Links:
Relates
relates to MGNLCI-6 Only detect files with an .xml suffix Closed
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Basel 63
Story Points: 1

 Description   

Currently the importer only works if the dir specified with magnolia.content.bootstrap.dir is the same as magnolia.resources.dir, or a subdirectory of it.

Conceptually this is strange for a developer, since the magnolia.resources.dir is known as the location that holds the light modules. It should be possible to specify any directory in magnolia.content.bootstrap.dir


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