[MAGNOLIA-3178] Several modules have a dependency from the cache module also when this should not be required Created: 06/Apr/10  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: cache
Affects Version/s: 4.3.1
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Fabrizio Giustina Assignee: Magnolia International
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-2258 Remove dependency on exchange-simple/... Closed
dependency
is depended upon by MGNLDATA-100 Make dependency on the cache module o... Closed
is depended upon by MGNLDMS-183 Make dependency from the cache module... Closed
is depended upon by MGNLINTEMPL-15 Make dependency from the cache module... Closed
is depended upon by MGNLRES-25 Make dependency from the cache module... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Opening this issue to link together all the specific issues already traced in other modules.

Several modules have now a non-optional dependency on the cache module and can't work if the cache module is not installed.
This is just because they need to register their own workspace for flushing (so it's just for a configuration required by the cache module), but since they use a task which is inside the cache module for this, the dependency becomes required.

At the moment this have been fixed by catching the exception thrown when trying to instantiate the task, since we couldn't find a better solution. Considered options are:

  • move the cache flushing task to core, but it's undesidered since all the modules will now only depend on the last magnolia core containing such task (4.3.2?)
  • copy the cache flush task to each single module (pretty bad for the duplication of code)
  • use reflection to instantiate the task? Not better than catching the exception


 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

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