Several modules have a dependency from the cache module also when this should
not be required
----------------------------------------------------------------------------------------------
Key: MAGNOLIA-3178
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3178
Project: Magnolia
Issue Type: Bug
Affects Versions: 4.3.1
Reporter: Fabrizio Giustina
Assignee: Boris Kraft
Priority: Minor
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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
