[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
info.magnolia.module.model.reader.ModuleDependencyException: Module Magnolia Standard Templating Kit Demo Project (version 2.0.7) is dependent on standard-templating-kit version 2.0.7, but Magnolia Standard Templating Kit Module (version 2.0.8) is currently installed.

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:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

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,
The Magnolia Team

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