[MAGNOLIA-3803] When instance fails to start due to unsatisfied module dependencies, list all of them not just the first one Created: 18/Aug/11 Updated: 11/Dec/13 Resolved: 11/Dec/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | modulemechanism |
| Affects Version/s: | 4.4.4 |
| Fix Version/s: | 4.4.11, 4.5.9 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Jan Haderka | Assignee: | Federico Grilli |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | next | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| 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)
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
or provide script to perform module dependency checks so that one can ensure all deps are satisfied w/o having to restart magnolia multiple times. |
| Comments |
| Comment by Magnolia International [ 11/Dec/13 ] |
|
Fixed with |