[MGNLDAM-135] Use same Jackrabbit version as core Created: 20/Feb/13  Updated: 22/Feb/13  Resolved: 21/Feb/13

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Major
Reporter: Daniel Lipp Assignee: Eric Hechinger
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLSTK-1097 Tests fail after upgrade to Jackrabbi... Closed
relation
is related to MAGNOLIA-4846 Upgrade to Jackrabbit 2.6 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

 Description   

With MAGNOLIA-4846 we upgraded core to use Jackrabbit 2.6.0 Unfortunately DAM defines it's on Jackrabbit version (2.4.3. right now).
We have to make sure these versions are aligned. Hence we should either just drop the definition in DAM (DAM would then get the jr version defined in core) - or, if for any reason required, update DAM's JR version to 2.6.0 as well.


Generated at Mon Feb 12 04:56:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.