[MAGNOLIA-1927] ModuleBootstrapTask should not bootstrap recursively anymore Created: 06/Dec/07  Updated: 23/Jan/13  Resolved: 06/Dec/07

Status: Closed
Project: Magnolia
Component/s: updatemechanism
Affects Version/s: 3.5 RC2
Fix Version/s: 3.5 RC3

Type: Improvement Priority: Major
Reporter: Vivian Steller Assignee: Vivian Steller
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MAGNOLIA-1926 New bootstrap mechanism: bootstrap mo... Closed
supersession
supersedes MAGNOLIA-1354 Module bootstrapping could accidental... 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)

 Description   

This is a consequence of MAGNOLIA-1926. Subfolders will be used (per default, but configurable in your own ModuleVersionHandler of course) to bootstrap files for dependent modules and/or for different versions (deltas) of bootstrap files (the latter is not decided yet).

Even more, having bootstrap files in /mgnl-bootstrap/config/config.xyz... instead of directly /mgnl-bootstrap/config.xyz... is just redundant information and did not imply anything special except "structuring".



 Comments   
Comment by Vivian Steller [ 06/Dec/07 ]

fixed with r13404.

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