[MAGNOLIA-4066] clean up version handler: CoreModuleVersionHandler should become a DefaultModuleVersionHandler Created: 09/Feb/12 Updated: 10/Mar/21 Resolved: 10/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 4.5 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Daniel Lipp | Assignee: | Unassigned |
| Resolution: | Outdated | 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)
|
| Description |
|
Caution: be aware that right now CoreModuleVersionHandler defines a rather sophisticated order of reading bootstrap files and executing coded tasks. Hence it can be very time consuming to change/fix things in there. This would be much more straightforward, when using DefaultMVH's default behavior of bootstrapping all files in the module's bootstrap folder order. Unfortunately this would be quite an effort. |