[MAGNOLIA-4755] Improve module dependency warning logs for exact versions Created: 21/Dec/12 Updated: 19/May/22 Resolved: 19/May/22 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core, updatemechanism |
| Affects Version/s: | 4.5.7 |
| Fix Version/s: | 4.5.x |
| Type: | Improvement | Priority: | Trivial |
| Reporter: | Natascha Desmarais | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | installation, logging, module_dependency | ||
| 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)
|
| Date of First Response: |
| Description |
|
When a module is requiring an exact version of another module, the current log warning might be a little confusing. For example: ERROR info.magnolia.init.MagnoliaServletContextListener : Oops, Magnolia could not be started So maybe in this case it would be better to state that the module is expecting an exact version - the above message is a little confusing since it might not be clear why a higher version is "bad". |
| Comments |
| Comment by Roman Kovařík [ 19/May/22 ] |
|
Hello, This ticket is now marked as closed due to one of the following reasons:
If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you. Thank you, |