[MGNLCACHE-47] Duplicated bootstrap XMLs in magnolia-module-cache JAR Created: 21/Jun/10  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Cache Modules
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Jozef Chocholacek Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

There are 2 xml files in mgnl-bootstrap/cache/setup folder of magnolia-module-cache-4.3.1.jar file (config.modules.cache.config.configurations.default.executors.store.cacheContent.compressible.xml and config.modules.cache.config.configurations.default.executors.store.serveContent.xml). These files define exactly the same content that is previously defined in config.modules.cache.config.configurations.default.xml file in the parent mgnl-bootstrap/cache folder.
This causes problems when initializing the module using ModeShape JCR repository instead standard Jackrabbit one. After removing both files from the setup subdirectory, the initialization proceeds OK.

This causes problems only with ModeShape repo which I am developing, and the real problem is in ModeShape itself (see https://jira.jboss.org/browse/MODE-788), but the duplicity is IMHO unnecessary.



 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 Sun Feb 11 23:51:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.