[MAGNOLIA-2503] module bootstrap: bootstrap files in subfolders automatically Created: 09/Dec/08  Updated: 23/Jan/13  Resolved: 17/Feb/09

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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:

 Description   

In Magnolia 3.0, files in mgnl-bootstrap/moduleName and subfolders thereof were bootstrapped. This is not the case anymore since 3.5, which is annoying, if once has many bootstrap files (dialogs, paragraphs, ...) and wants to structure in sub folders.

Unfortunately, if we re-enable this, we'll have to modify some modules (core, workflow), since they were using this as a "feature", i.e as a location for optional bootstrap files. The new suggested location would be the setup package of the module.



 Comments   
Comment by Magnolia International [ 17/Feb/09 ]

Javadoc of info.magnolia.module.delta.ModuleDependencyBootstrapTask needs to be fixed/updated accordingly.

Comment by Magnolia International [ 17/Feb/09 ]

Fixed Javadoc.

As a side note, I'm not convinced by this implementation, which severely limits the location where one wants to put their bootstrap file. (i.e they can't use their own package name for instance)

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