[MAGNOLIA-2762] ModuleRegistry : throw an exception for unknown modules Created: 04/Jun/09  Updated: 23/Jan/13  Resolved: 16/Feb/10

Status: Closed
Project: Magnolia
Component/s: core, updatemechanism
Affects Version/s: None
Fix Version/s: 4.3

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
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 MGNLNEWSLETTER-4 Fix renaming issue 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   

An exception should be thrown when attempted to get unknown modules.
Care needs to be taken - some code checks if a module is present (see InstallContext for instance) - but ideally the methods of ModuleRegistry should be consistent in how they treat absent module. Maybe we'll need to expose a new method to check for modules' existence.

For 4.1 we'll simply issue a warning to avoid breaking the api.


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