[MAGNOLIA-2006] Jackrabbit 1.4 support Created: 15/Jan/08  Updated: 23/Jan/13  Resolved: 04/Jun/08

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.5.3
Fix Version/s: 3.6

Type: Task Priority: Major
Reporter: Fabrizio Giustina Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-2717 CopyUtil not able to restore versione... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Jackrabbit 1.4 is out: unfortunately the Provider implementation used for jackrabbit 1.3 is not binary compatible with jackrabbit 1.4, although it is source compatible (it just needs to be compiled with the appropriate jackrabbit version).

In order to support jackrabbit we should create a different provider implementation (two modules compiled with two different jackrabbit versions, not really nice) or doing some dirty hack using reflection (should be just a single method call actually).

PS: I've been testing snapshots builds from jackrabbit 1.4 for a few months in a clustered environment and it looks very good (faster, never had memory issues)



 Comments   
Comment by Philipp Bracher [ 24/Apr/08 ]

First commit done but without intensive testing

Comment by Fabrizio Giustina [ 26/Apr/08 ]

Note that the real problem is supporting both jackrabbit 1.3 than 1.4.. The provider compiled with jackrabbit 1.4 will not work anymore with 1.3, is that ok?

Comment by Magnolia International [ 04/Jun/08 ]

Added a profile in magnolia-core for the 3.5 branch which allows building core against JR1.4
For 3.6, we won't support JR1.3 unless really needed (in which case we'll either add a profile too)
We could split the JR provider out of core, but that requires a bit more work, as the RepositoryTestCase in core currently rely on the ProviderImpl (and simply taking it out creates a cyclic dependency)

Comment by Magnolia International [ 04/Jun/08 ]

Also updated trunk to use jackrabbit-core-1.4.4

Comment by Philippe Marschall [ 10/Jun/08 ]

Would it be possible to have two artifacts? One with a classifier jackrabbit14 and one with a classifier jackrabbit13.

Comment by Magnolia International [ 10/Jun/08 ]

That's exactly what you get when you build core on the 3.5 branch with the jackrabbit14 profile. (well, only one of the artifacts as a classifier)
As i said, we're not too keen on supporting jr13 with 3.6, so we probably won't do this on the trunk or integrate this in the regular build.

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